Defect Report | Priority and Severity

Defect Report: 

  • If application is not working as expected we can report that as defect in defect report. 
  • A defect report is a document that has concise details about what defects are identified, what action steps make the defects show up, and what are the expected results instead of the application showing error (defect) while taking particular step by step actions.
  • Defect Reporting, Defect Tracking, and Status Tracking is called Defect Management. Some companies use Manual Process (Excel workbook), and some companies use Tool-based processes for Defect Management. 
  • Defect Management Tools Examples: Bugzilla / Issue-Tracker / PR-Tracker etc.
    Important fields of a Defect Report template:
  • Defect Id :  It is a unique number for every defect we found while testing.
  • Summary :  Full description of the defect .
  • Detected By : Name of the tester who found the defect .
  • Assigned to :  Currently the defect is assign to whom. When a tester found a defect the it has to assign to any developer.
  • Severity : Severity defines how impactful a bug can be to the system. It can values either high or medium or low specifies the seriousness of the defect.
  • Priority : Priority indicates how soon the bug should be fixed. It can values either high or medium or low specifies the importance of the defect or functionality. The defect are fixed based on priorities.

    Defect Status in defect life cycle is the present state from which the defect or a bug is currently undergoing. The goal of defect status is to precisely convey the current state or progress of a defect in order to better track and understand the actual progress of the defect lifecycle. 
  • Build version : It show currently build version in which we are testing. We  can check this from release note document. 
  • Module : In which module the defect is found.
  • Environment :  The defect is found in which environment like : Test environment, UAT or Production environment.
  • Defect Type :  Specify the type of defect like functional , network , data , performance or UI ( User Interface) etc.
  • Reproduceable : It has value either YES or NO:
                YES: Every time the defect is occurring .
                NO: Most of the time its working correctly, only few cases it is failing and not able to reproduce  
  • ( If the defect is non reproduceable we can take screen shot of the defect and report it along with the defect.)
  • Reproduce Steps : Specify the navigation steps to reproduce the defect.

No comments:

Post a Comment