We need to verify the status of every file in /tests/visual in the master branch.

This must be done against a checkout from git in master.

The outcome of this should be two lists:

Tests that should be converted to unit tests

Anything that's not purely visual or extremely hard to unit test should be moved to a unit test and the visual test page should be removed.

You don't need to write any of these unit tests, we just need a list.

Tests that are currently failing

If the test is from a ticket and the ticket is still open, just make sure the ticket mentions that there is a visual test page.

All tests

fill this out prior to starting any testing to avoid duplicated efforts

Enter your name in the browser cells and change the color to green when the tests are complete.

Tests to convert to unit tests

• /visual/button/button_performance.html
• Chrome, (all): This test just reports a time value, it does not need to be viewed in total, however I'm not sure there is an "exact" value to test.
• /visual/button/button_disabled_true.html
• Chrome, (all):  This test is extra -- all the functionality tested and more is contained in the /visual/button/button.html by pressing disabled.

Failing tests

• (none yet)

Testers

Fill in as much or as little info as you want. We really just need to reduce the size of what we're using as handles to mark who owns which tests and a way to get in contact with you in case there are any questions.

Questions? Ping Scott on jabber: scott.gonzalez@gmail.com