I N T R O D U C T I O N
Systematic and comprehensive testing is known to be a major factor contributing to Information Systems Quality. Adequate testing is however often not performed, leading to a higher number of software defects which impact the real and perceived quality of the software, as well as leading to time and expense being spent on rework and higher maintenance costs.
How to Write Software Test Documentation is a plain-English, procedural guide to developing high quality software test documentation that is both systematic and comprehensive. It contains detailed instructions and templates on the following test documentation:
Test Design Specification,
Test Item Transmittal Report,
Test Incident Report,
Test Summary Report,
How to Write Software Test Documentation is derived principally from IEEE Std 829-1983 Standard for Software Test Documentation. It contains clear instructions to enable project staff with average literacy skills to effectively develop a comprehensive set of software test documentation.
How to Write Software Test Documentation
Plain English version of IEEE Std 829
Publication date: 22.04.2011
Practical guide for software development project managers and staff
El vendedor asume toda la responsabilidad de esta entrada.