Defect Reporting

Defect Reporting, Finding defects, choosing defect report tool or template, writing defect reports, tracking defect status, change-related testing, and closing defects.

Defect Reporting & Tracking

During Test execution If Test Engineers/Testers find any mismatches, send Defects Reports to Developers

Sample Defect Report Template

1) Defect ID: Unique No or Name

2) Description: Summary of the defect

3) Feature: Module / Function / Service, in these module TE found the defect

4) Test Case Name: Corresponding failing test condition

5) Reproducible (Yes / No): Yes -> Every time defect appears during test execution
No -> Rarely defect appears

6) If Yes, attach the test procedure:

7) If No, attach snapshot & strong reasons:

8) Status: New / Reopen

9) Severity: Seriousness of defect w.r.t functionality (high / medium / low)

10) Priority: Importance of the defect w.r.t customers (high / medium / low)

11) Reported bug: Name of Test Engineer

12) Reported on: Date of submission

13) Assign to: Name of the responsible person in development team -> PM

14) Build Version ID: In which build, Test Engineer fount the defect

15) Suggested fix (Optional): Tester tries to produce a suggestion to solve this defect

16) Fixed by: PM or Team Lead

17) Resolved by: Developer name

18) Resolved on: Date of solving By Developers

19) Resolution type: check out in next page

20) Approved by: Signature of Project Manager (PM)

Defect Age: The time gap between “reported on” & “resolved on”


Defect Status Cycle:

New: When a new defect is logged and posted for the first time. It is assigned a status as NEW.

Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team

Open: The developer starts analyzing and works on the defect fix

Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as “Fixed.”

Pending retest: Once the defect is fixed the developer gives a particular code for retesting the code to the tester. Since the software testing remains pending from the testers end, the status assigned is “pending retest.”

Retest: The tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and changes the status to “Re-test.”

Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed and the status assigned is “verified.”

Reopen: If the bug persists even after the developer has fixed the bug, the tester changes the status to “reopened”. Once again the bug goes through the life cycle.

Closed: If the bug is no longer exists then tester assigns the status “Closed.”

Duplicate: If the defect is repeated twice or the defect corresponds to the same concept of the bug, the status is changed to “duplicate.”

Rejected: If the developer feels the defect is not a genuine defect then it changes the defect to “rejected.”

Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status “Deferred” is assigned to such bugs

Not a bug: If it does not affect the functionality of the application then the status assigned to a bug is “Not a bug”.

Defect Resolution:

After receiving defect report from Testers, developers review the defect & send the resolution type to Tester as a reply

01) Duplicate, rejected due to the defect is same as previously reported defect
02) Enhancement, rejected due to the defect is related to the future requirement of customer
03) H/w limitation, rejected due to the defect raised w.r.t limitation of H/w devices
04) S/w limitations, rejected due to the defect raised w.r.t limitation of S/w Techno
05) Not applicable, rejected due to the defect has no proper meaning
06) Functions as designed, rejected due to coding is correct w.r.t to designed doc’s
07) Need more information, not (accepted/rejected) but developers require extra information to understand the defect
08) Not reproducible, not (accepted/rejected) but developers require a correct procedure to reproduce the defect
09) No plan to fix it, not (accepted/rejected) but developers want extra time to fix
10) Fixed, developers accepted to resolve
11) Fixed indirectly, accepted but not interested to resolve in this version (default)
12) User misunderstanding, need extra negotiation between testing & development team.


Types of Defects:

01) User Interface bugs (low severity):

1) Spelling mistakes (high priority)
2) Improper alignment (low priority)

02) Boundary related bugs (medium severity)

1) Doesn’t allows valid type (high priority)
2) Allows invalid type also (low priority)

03) Error handling bugs (medium severity)

1) Doesn’t providing error message window (high priority)
2) Improper meaning of error message (low priority)

04) Calculations bugs (high severity)

1) Final output is wrong (low priority)
2) Dependent results are wrong (high priority)

05) Race condition bugs (high severity)

1) Dead lock (high priority)
2) Improper order of services (low priority)

06) Load conditions bugs (high severity)

1) Doesn’t allow multiple users to access / operate (high priority)
2) Doesn’t allow customers accepted load (low priority)

07) Hardware bugs (high severity)

1) Doesn’t handle device (high priority)
2) Wrong output from device (low priority)

08) ID control bugs (medium severity)
1) Logo missing, wrong logo, Version No mistake, Copyright window missing,
Developers Name missing, Tester Name missing

09) Version control bugs (medium severity)
1) Differences between two consecutive build versions

10) Source bugs (medium severity)
1) Mistake in help documents – Manual support

Defect Reporting


Software Test Documents
Test Strategy Document
1. Test Plan Document
2. Test Case Document
3. Defect Report Document
4. Test Metrics Report
5. Test Summary Report
Follow me on social media:

Leave a Comment