The overall framework for our test efforts:
-1) document smoke tests for all core modules (ie, list of commands
such as, go to page x, click on y, expect to see z)
0) execute manual smoke tests for all core modules
1) Integrate tclwebtest and acs-automated-testing
2) create tools/documentation to make it easier to create and
contribute automated tests. (main tool would be some kind of macro
recorder. Docs would include more examples)
3) write automated smoke tests for all core modules
There are two different documents for -1, one from PeterM (http://dotlrn.collaboraid.net/test/plan) and one from
Dierdre at MIT (online?), which need to be merged and made more public, and we
need to make it very easy for anybody to contribute (ie, through
posting comments, etc)
Most of the effort for 0) in 5.0 has been from MIT.
Item 1) is scheduled to happen in mid-february at the Berlin code
bash. Prep work would be great, and would include improving any
existing docs on tclwebtest and acs-automated-testing, surveying other
automated testing tools for a) GPL code we can use b) design we can
use.
