IEEE Test Incident Report

1.1 Purpose

To document any event that occurs during the testing process that requires investigation.

1.2 Outline

A test incident report shall have the following structure:

a) Test incident report identifier;

b) Summary;

c) Incident description;

d) Impact.

The sections shall be ordered in the specified sequence. Additional sections may be included at the end. If some or all of the content of a section is in another document, then a reference to that material may be listed in place of the corresponding content. The referenced material must be attached to the test incident report or available to users of the incident report.

Details on the content of each section are contained in the following subclauses.

1.2.1 Test incident report identifier

Specify the unique identifier assigned to this test incident report.

1.2.2 Summary

Summarize the incident. Identify the test items involved indicating their version/revision level. References to the appropriate test procedure specification, test case specification, and test log should be supplied.

1.2.3 Incident description

Provide a description of the incident. This description should include the following items:

a) Inputs;

b) Expected results;

c) Actual results;

d) Anomalies;

e) Date and time;

f) Procedure step;

g) Environment;

h) Attempts to repeat;

i) Testers;

j) Observers.

Related activities and observations that may help to isolate and correct the cause of the incident should be included (e.g., describe any test case executions that might have a bearing on this particular incident and any variations from the published test procedure).

1.2.4 Impact

If known, indicate what impact this incident will have on test plans, test design specifications, test procedure specifications, or test case specifications.

Tags: IEEE Test Incident Report, incident description, INCIDENT REPORT, test incident, Test Incident Report, test procedure specification