Documentation based software testing

Testing is sometimes viewed as an add on step in software development - something you do to demonstrate that the product is ready for use. Test planning is often postponed until the development is near its end. This results in incomplete testing, ambiguous test results, and the release of products of doubtful quality. After reviewing fundamental software testing issues, we describe a document-driven testing approach in which test plans and test result evaluation are done with the aid of documentation prepared throughout the design process. The policies about testing, and response to test results are determined in advance and high quality standards can be enforced on a project.