Please correct me if I'm wrong, but it seems that this group's purpose is to concentrate on unit testing and code coverage. Excellent. This is a definite sign of maturity for Drupal.
But I also see some posts in here that refer more to UI centric testing. Is there yet an effort for organizing this testing as well?
Unit testing is a great way to find problems that may not always be obvious in the UI, but they are not always the best way to catch problems which may be obvious in the UI. For example, the unit tests for the forms API may confirm that the form tokens are being generated properly but not pick up on the fact that another module alters the token (making this up here :) and so the form submission ultimately fails. At the end of the day, you really need to run through use cases to make sure it all works.
Typically, folks will run functional/UI tests by hand (create, edit, delete a node by hand, etc...). This is OK, but not ideal. Manual testing is time consuming and difficult to reproduce.
I've done testing of applications where automation was not an option, and as standardized as I tried to make the list of tests I ran, they were never run the same way twice, leaving little crevices for regression to creep through.
I believe we should consider trying to automate UI testing as well as unit testing. This would give us a gorgeous set of regression tests.
I guess my main question is whether this is the place/time to bring that up. I don't think it would take any attention/resources away from the unit testing efforts here.