Description: ------------ After the redesign of the page all the tests that test against the layout fail horribly, we have to get them up to standard before the next release.

A good chunk of the tests have been updated but still don't pass because the expectf in pear test is frankly rather bad. I've discussed this with Greg and he came up with some good ideas which we'll be looking into, hopefully for pear 1.8 (and obviously pyrus), so until then I'm keeping the ticket open and perhaps adding 1.19.0 milestone on it since we can't really finish this before 1.18.0

I don't suppose there would be any chance of heading towards a Selenium style test suite for the layout/UI components? Our work application benefits reasonably well from it, and the test writing requirements are less. For instance, a test becomes: SignupTest - Load this URL - Click these controls - Inspect the database for objects/records to have been created ... rather than picture perfect rendering.

I made small inroads here.