#7 Write test plan
It would be very helpful if we had a test suite which we could run through to make sure SK won't explode. A few brief examples:
1) Install SK with pre-existing OMF files installed
2) Install SK with no pre-existing OMF files installed
3) Upgrade SK with pre-existing OMF files installed
4) Upgrade SK with no pre-existing OMF files installed
5) Upgrade SK on a system where /var/lib/scrollkeeper was deleted
6) Install an empty OMF file and run scrollkeeper-update
7) Install an invalid OMF file and run scrollkeeper-update
8) Install an OMF file pointing to HTML file
9) Install an OMF file pointing to PS file
10) Install an OMF file with invalid <identifier>
11) Install an OMF file with invalid <language>
12) Install an OMF file with a missing <identifier>
13) Install an OMF file with a missing <language>
...
Of course this is a lot of work to do, but we really should do it.
Let's put this in CVS in scrollkeeper/doc/testing/TEST_PLAN
Then, as we come up with more tests, we add them to the bottom.
Then we need a way to keep track of whether the tests were performed, when, and what the results were (pass/fail, comments). For now, lets put
this into another text file: scrollkeeper/doc/testing/testing_log.txt
Logged In: YES
user_id=72575
Scrollkeeper will be shipped as part of Gnome by Sun on
Solaris. Everything shipped by Sun has to go through
rigorous testing and a test plan written for it. I will
write the test plan, Sun test engineers will write the
assertions (I will assist them with this) and automate the
tests (hopefully). This should be started in the next 2-3
weeks. The tests will be run regularly together with other
Gnome related tests by the Sun test team.
Logged In: YES
user_id=943591
i think may ease workload