In software testing company working on volume testing, load testing and performance based testing, do not give even a little importance to the documentation as much as they give to the software development process. However, the fact is projects that have all the documents have a high level of maturity and careful documentation can save an organizationās time, effort and money.
Test documentation is documentation of artifacts created before or during the testing of software. It helps the testing team to estimate testing effort needed, test coverage, resource tracking, execution progress, etc. It is a complete suite of documents that allows you to describe and document test planning, test design, test execution, test results that are drawn from the testing activity. For a newbie, itās easy to assume that Testing is executing the various section of code on an ad-hoc basis and verifying the results. But in the real world, Testing is a very formal activity and is documented in detail. Test Documentation makes planning, review, and execution of testing easy as well as verifiable.
The degree of test formality depends on
- The type of application under test
- Standards followed by your organization
- The maturity of the development process.
Testing activities generally consume 30% to 50% of software development project effort. Documentations help to identify Test process improvement that can be applied to future projects.
There is the necessary reference document, which is prepared by every test engineer before stating the test execution process. Generally, we write the test document whenever the developers are busy in writing the code. Once the test document is ready, the entire test execution process depends on the test document. The primary objective for writing a test document is to decrease or eliminate the doubts related to the testing activities.
If the testing or development team gets software that is not working correctly and developed by someone else, so to find the error, the team will first need a document. Now, if the documents are available then the team will quickly find out the cause of the error by examining documentation. But, if the documents are not available then the tester need to do black box and white box testing again, which will waste the time and money of the organization. More than that, Lack of documentation becomes a problem for acceptance.