6.3 Test Logs and Incident Reports

---

The next two items on the deliverables checklist, test logs and incident reports, are completed by the Test Team during execution of the tests. Chapter 5 described what a test log should contain. As a brief recap, each log entry should contain the following information:

• Execution descriptions

• Procedure results

• Environmental information

• Unexpected events

• Incident report ID number

Figure 6.3 (following page) is a recommended template for creating an incident report. Incident reports should follow the IEEE Standard 829-1998 guidelines. These guidelines call for the following items to be present in a test report:

• Incident report ID number

• Summary

• Input

• Expected results

• Actual results

• Anomalies

• Date and time of the incident

• Procedural step at which the incident occurred

• Environmental conditions

  
  Figure 6.3: Incident Report.

• Documentation of any attempts to repeat or re-create the problem

• Names of the testers and observers

• Impact the incident had on the test plan or specifications

  “Today, there is no question that if a software product has not been tested, it will not work. It is equally true, however, that once a program has been tested, the odds that it will work correctly under all conditions are only moderately improved. We should think of testing like weeding a garden: individual bugs can be found with tests but more powerful methods are needed for the thickets. [10] ” –Watts Humphrey

---