Documents for testing are created at various phases. The following documents are considered in relation to these.
Before Testing
Since the creation of test cases marks the start of testing. The aforementioned documents are necessary for reference.
SRS –
Functional Requirements document
Test Policy document –
It mandates extensive testing of the product prior to release.
Test Strategy –
The test strategy document outlines the specifics of the team’s testing, the matrix of responsibilities, and the roles and responsibilities of the test manager and test engineer.
Document
Traceability Matrix –
This SDLC document relates to the requirements collection procedure. This matrix is updated with additional needs as they arise. You can follow them both forward and backward. These matrices aid testers in identifying the requirement’s source.
During Testing:
While testing is started and is being done, these following documents may be required.
Test Case document –
It contains the list of to be tests. It includes various testing like: Unit test plan, Integration test plan, System test plan and Acceptance test plan.
Test description –
It is a detailed description of all test cases and procedures to executing them.
Test case report –
It contains test case report resulting from the test.
Test logs –
It contains test logs for every test case report.
After Testing:
After testing, the only thing left is the test summary, which is an analysis of all test reports and logs together. When preparing the program for release, the version control system makes it available. It wraps up and determines the program’s readiness for release.
Advantages of Software Testing Documentation
- The quality of procedures and aims is made clearer through documentation.
- When a client employs a software application, it guarantees internal cooperation.
- It guarantees that the steadiness of duties and performance are made clear.
On preventive tasks, it offers feedback. - It offers suggestions for your planning cycle.
- It produces unbiased proof of the quality management system’s effectiveness.
Drawbacks of Software Testing Documentation
- Due to the need to preserve both the customer’s modifications and parallel document changes, it can be a little laborious.
- An improperly written test report will mirror the application’s quality.
- There are occasions when someone without product knowledge writes it.
- The document may occasionally cost more than it is worth.
If you want to read my article, visit:- SoftwareTestingLeaders.com
If you want to read my story, visit:- Monkey Testing In Software
