Defect Report Format in IEEE 829 – Manual Testing Training

 

Defect Report Format in IEEE 829 – Manual Testing Training

 

g)  Defect Report Format in IEEE 829:

 

1. Defect ID :

Unique number or name.

 

2. Defect description :

About defect.

 

3. Sprint build version number :

Version number of sprint build in which build this defect was defected .

 

4. Feature :

Name of module in which module this defect was detected.

 

5. Failed test case :

ID of failed scenarios and cases in which case execution this defect was found.

 

6. Severity :

The seriousness of defect w.r.t tester

High/ critical/ show stopper–> Not able to continue further testing  unit fix this defect.

Medium / Major –> Able to continue further testing , but mandatory to fix defect.

low/ Minor –>  Able to continue further testing and may or may not to fix defect.

 

7. Priority:

The importance to fix this defect w.r.t  customer high , medium , low.

 

8. Test environment :

Information of used hardware and software while detecting this defect.

 

9. Reproducible :

10. If yes , attach test case document.

 

11. If no, attach test cases document and sprint screen shot , which show defect.

 

12. Status :

New –> Reporting first time.

Reopen–> Re-reporting  .

 

13. detected by:

name of the tester.

 

14. Detected on :

Date and time for reporting.

 

15. Assigned to :

Name of developer.

 

16. Suggested fix (optimal) :

Suggestions to fix this defect.

 

Note 1 :

Ms- excel/ open office excel is better software to prepare defect report by testers.

 

Note 2 :

Ms-outlook / lotus notes is the best software to forward defect report to developer and CC to PO, SM , SH as an email.

 

 

In this article we have seen Defect Report Format in IEEE 829 – Manual Testing Training . In the next article will see Defect Tracking Process, Test case related defect fixing, Test data related defect fixing, Test environment related defect fixing, Coding related defect or bug fixing, Bug life cycle ( BLC), and Test Cycle vs Bug age.