Testing Documentation - Software Testing

Testing documents are prepared at different stages. These documents are discussed as follows.

1. Before Testing:

Since testing begins with the generation of the test cases. The following documents are required for reference –

• SRS document - Functional Requirements document.
• Test Policy document - It means the product must be tested far before release.
• Test Strategy document - It mentions detailed aspects of test the team, responsibility matrix, and rights/responsibilities of the test manager and test engineer.
• Traceability Matrix document - This is SDLC document, that 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 the requirement.

2. During Testing:

While testing is started and is being done, the 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 for executing them.
• Test case report - It contains a test case report resulting from the test.
• Test logs - It contains test logs for every test case report.

3. After Testing:

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

Use Cases of Testing Documentation

Here is the Use Case Scenario for each stage – Project: Online Shopping Mobile App

1. Before Testing

Testing documents prepared before actual testing starts.

Use Case Scenario (Before Testing): The team is preparing to test the new version of the “ShopFast” mobile app.

• The SRS document says: “Customer shall be able to apply coupon code and see discounted price before payment” and “Guest checkout must be allowed without login”.
• The Test Policy document of the company states: “No release is allowed if critical or high severity defects are open and code coverage is below 80%”.
• The Test Strategy document mentions: There will be 5 manual testers and 2 automation engineers. Test Manager approves the exit criteria, Test Lead distributes daily tasks, and every tester has the right to stop testing if the build is unstable.
• The Traceability Matrix document already maps requirement “REQ-045: Apply Coupon” to future test cases TC_101, TC_102, TC_103 and shows the original source as “Client meeting dated 10-Nov-2025”.

At this stage, no testing has started yet, only planning and reference documents are ready.

2. During Testing

Testing is running daily, defects are being found and fixed.

Use Case Scenario (During Testing): Testers are executing test cases on the “ShopFast” app version 3.5 build 112.

• The Test Case document contains the list, for example:

Test Case ID: TC_150

Description: Verify guest user can place order worth ₹2,499 with coupon “WELCOME100” and free shipping is applied.

• The Test description gives full steps:

Preconditions → Open app → Add product of ₹2,599 to cart → Proceed as Guest → Enter coupon WELCOME100 → Verify final amount becomes ₹2,499 and “Free Shipping” banner appears → Complete payment.

• After execution, the Test case report is updated:

TC_150 → Failed (Actual result: Discount applied but shipping charge ₹99 still added). Defect ID DEF-0892 raised.

• The Test logs automatically record:

2025-12-09 11:22:10 – Entered coupon WELCOME100

2025-12-09 11:22:12 – Discount ₹100 applied

2025-12-09 11:22:15 – Shipping charge ₹99 still visible (screenshot attached).

Testing is live, documents are continuously updated every day.

3. After Testing

All planned testing is completed, no more execution.

Separate Use Case Scenario (After Testing): Regression testing of “ShopFast” app version 3.5 is finished. All defects are closed. Only one final document is prepared now — the Test Summary Report. It contains:

• Total test cases planned: 820
• Executed: 820
• Passed: 812
• Failed: 0 (8 earlier failed cases are retested and passed after fix)
• Defects found during whole cycle: 87 (12 Critical, 25 High, 50 Medium/Low) → all resolved
• Overall pass percentage: 100%
• Test coverage: 94%
• Environment: Android 13, iOS 18, real devices + simulators

Conclusion in the report: “ShopFast Mobile App v3.5 is stable, meets all exit criteria, and is recommended for release to Play Store and App Store.”