toaster - David Reyna is looking into selenium automation but likely won't be tested without automation Bug 9132 has some previous discussions.
This was also discussed under Bug 12972. My current strategy is to get the Selenium test under Travis working again, and then go from there.
Also, see about adding the test to auto-builder since it is documented and in-house.
I plan to leverage as a fundamental command line unit test to install and run Toaster against "quilt-native". This unit test easy to wrap with a trivial ptest, but still covers the most vulnerable and shift-able part of the Toaster interface, that being its basic connection to bitbake and the ability to execute build commands. Getting the Selinium test suite running is a secondary task, and will require more effort.
This case is replaced by full testing support via STF effort.