Testing Documentation in Software Engineering

Testing documents are prepared at different stages. These documents are discussed as following below.

1. Before Testing:
Since testing begins with the generation of the test cases. These are following documents are required for reference –

  • SRS document
    Functional Requirements document.

  • Test Policy document –
    It means product must be tested far before releasing.

  • Test Strategy document –
    It mentions detail aspects of test the team, responsibility matrix and rights/responsibility of the test manager and test engineer.

  • Traceability Matrix document –
    This is SDLC document, which is related to the requirements gathering process. As new requirements come, they are added to this matrix. They can be traced forward and backward. These matrices help testers know the source of requirement.

2. 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.

3. After Testing:
After testing, only test summary remaining which is collective analysis of all test reports and logs. The software is released under version control system if it is ready to launch. It summarizes and concludes whether the software is ready to launch.

Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.

My Personal Notes arrow_drop_up

If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.

Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.