4.4 Test Incident Reporting Process
The process is used for the reporting of test incidents (Often called defects). So if you find incidents while testing your software you will enter this process, or when a retest passes.
Purpose:
To report to the relevant stakeholders incidents requiring further action identified as a result of test execution. In the case of a new test this will require an incident report to be created. In the case of a retest, this will require the status of a previously-raised incident report to be updated, but may also require a new incident report to be raised where further incidents are identified.
Inputs to activities in this process may include:
- Test results
- Test procedures(s)
- Test Case(s)
- Test item(s)
- Test basis
- Test execution logs
Expected outcome of Test Incident Reporting Process:
- Test results are analysed
- New incidents are confirmed
- New incident report details are created
- The status and details of previously-raised incidents are determined
- Previously-raised incident report details are updated as appropriate
- New and/or updated incident reports are communicated to the relevant stakeholders
- Information items to be produced:
- Incident Report
4.4.1 Graphic overview of the Test Incident Reporting Process:
# | Activity | Tasks |
IR1 |
Analyse Test Results |
|
IR2 |
Create/Update Incident Report |
|