PHP: qa:runtests:todos

This is an old revision of the document!

12 August 2009

Investigate CI server - ongoing(S)
Use rtException everywhere, get rid of other exception classes (Z)
Research REDIRECTTEST (S)
Fix up any remaining test fails on S and G systems (S - to try again with Windows, G to try Windows, Z to work on G's Mac fail)
Completed writing documentation for parallel code on wiki (G)
Fully explain test results on 32 way system (G)
Run more tests on Valgrind (G - if time run tests with old and new verions. Will probably need to make a valgrind supression file)

Investigate CI server (S)
Tidy wiki and put together a set of doc pages (Z) (Note: user doc to go on wiki first, final destination undecided)
Use rtException everywhere, get rid of other exception classes (Z)
Research REDIRECTTEST (S)
Run existing code on Windows (Done - see results)
Fix up any remaining test fails on S and G systems (Z)
Start writing documentation for parallel code on wiki (G)
Run some more extensive tests/experiments with parallel code (G, Z&S to provide introductions)
Implement valgrind (Z)
Remove private, use protected (Z)

Run sequential groups within in Georg's schedulers (G - Done)
Write whole object to disk (check timing differences, if none leave as it, otherwise Win/Lin versions) (G - Done)
Refactor output writer - and task test group and task receiver. (G - Done)
Focus more on QA
- Assemble a set of standard tests (Z - Done, see QA/QATESTS.tgz + README)
- Checkin results for running them with old version and current version of our code (Z, done. See LinuxQAJuly18)
- Write phing task to compare them (S - done)
- Always run Unit tests before checkin (All)
- Add new unit test whenever we find a problem (All)
- Always check output for notices and warnings (All)
Always do clean checkout, never use cvs up (All)
Use rtException everywhere, get rid of other exception classes (Z - not done)