Defect Report template.

Defect Report template.

Defect Reports communicate issues discovered during test to project stakeholders. They offer information for teams to gain an understanding of the issue or error, to assist software developers to identify causes.

Creating a defect report template will guide testers to providing defect reports in relation to the use case being tested, with information that can be acted upon.

  Defect Report Template
Risk:Risk the issue has to the business and/or customer based on impact and likelihood.
Unique Test Number:Referencing the test case number used.
Product Name:Product or system under test.
Product version:When applicable.
Product Area:Area or feature of the product affected.
Dependencies:Browser, database type, other technical variations.
Description:A descriptive overview of the test scenario.
Test Intention:The specific test requirement.
Method:Prerequisites and instructions and steps to execute the test.
Expected result:Test outcome as per specification or user story.
Actual Result:Outcome of the test.
Supporting Evidence:Provide evidence that demonstrates the validity of the actual result.

The information needed to create effective default reports comes in part from the test case used to discover the fault. Further information is added to describe the outcome of the test, also including supporting test evidence such as screen shots and database results.

The purpose of a defect report is to help inform of possible issues. It’s important to use words carefully to remove any possible ambiguity, and to communicate constructively as opposed to a criticism.

Suggestions on how to fix an issue should not be included. If the information provided in the defect report is complete, developers will be able to analyse the fault successfully and provide technical solutions.

Tags: ,