11 Documentation Testing

Entry criteria: Before Documentation Testing can take place the system must have undergone Function Testing, Installation Testing and be fully integrated. Also, the Documentation must have been written.

Exit criteria: The process outlined below must be carried out, and a test report showing the documentation to be correct must have been generated.

Documentation Testing is performed by going through the documentation and performing each step relating to the use of the program. The Documentation Tester must examine the documentation for accuracy and verify its contents against the program. The Documentation Tester must also examine the Documentation for editorial clarity - that is correct spelling, grammar and clarity of instructions. During the test, the Documentation tester must make note of the following in the test report [1]:

• Is it easy to locate guidance within the document?
• Are the document table of contents and index accurate and complete?
• Are all error messages that may be displayed to the user described in the documentation?
• Are all the tool-tips or other in-program documentation accurate?

Some sections of the Documentation may have already been tested during Installation Testing (see section 10) or GUI Testing (see section 7) - these need only be performed once on the same version of code, and as such may be exempt if already listed in an Installation Test report or GUI test Report, however a note must be made in the Documentation Test report that these tests have already been done. Additionally, the user documentation will undergo a review process as explained in the SQAP in the Reviews section. This review will also help to ensure the correctness of the user documentation.