How to Document Test Execution?
The text execution process is conducted in the time of Integration and Installation stages.
But even for small projects testing process should be as formal as possible and comprise the suitable controls and documentation required to conduct the verification.
The process accepts that at this phase the items to be tested are controlled by Configuration Management.
The Test Item Transmittal Report dispatches items to be tested to Configuration Management and the testing company.
The test execution process generates the other 3 reports shown in the figure above:
- Test Log
- Test Summary Report
- Test Incident Report
Together these show what happens during testing, document any difference between what occurred and what was expected, and summarize the overall status of software testing.
The Test Item Transmittal Report is the formal relationship from the test producer to the testing company that items are prepared for testing. It determines all the parts which need to be tested.
Test Item Transmittal Report comprises:
- items to be tested
- their location
- Test Procedure Specification
- Test Plan
Especially significant is the Test Item Status, which describes deflections from the test item’s documentation or its test plan, or any fixes that have occurred since the last transmittal. Ultimately, it documents who gave approbation for transmittal into the testing function.
The Test Log is a simple chronological record of testing activity. The log records specific actions taken by software testers, defects and important incidents in the system.
Defects are simply noted in the Test Log but are minutely described in a Test Incident Report.
Test Incident Report contains such info:
- Who ran each test?
- When and in what environment was each test run?
- What was the outcome of test?
- What level of coverage is provided by each system test?
- How many defects have been found by each system test?
- How many times was each test run before it completed successfully?
The Test Incident Report documents any event that requires investigation. This means differences between what actually occurs and what is expected. This comprises program “bugs”, errors in user documentation, or any other type of trouble or anomaly.
A Test Summary Report provides a summary of the testing activities. Its goal is to estimate one or more test items and provide a basis for their acceptance.