Defect reporting

Uncategorized

Any mismatched functionality found in a application is called as defect/Bug/Issue.

During test execution test engineers are reporting mismatches as defects to developers through templates or using tools.

Defect reporting tools :

  • Clear quest
  • Dev track
  • Jira
  • Quality center
  • Bug zilla

Defect report contents :

  1. Defect is – Unique identification for the number for the defect
  2. Defect description – Detailed description of the defect including information about the module in which defect was found
  3. Version – Version of the application in which defect was found
  4. Steps – Detailed steps along with screenshots with which the developer can reproduce the defects
  5. Date raised – Date when the defect is raised
  6. Reference – Where in you provide reference to the documents like, requirement design, architecture or may be even screenshots of the error to help understand the defect
  7. Defected by – Name /ID of the developer who raised the bug
  8. Status – Status of the defect, more on this later
  9. Fixed by – Name /ID of the developer who fixed the defect
  10. Date closed – Date when the defect is closed
  11. Severity – Which describes the impact of the defect on the application
  12. Priority – Which is related to defect fixing urgency. Severity and priority could be high/medium/low based on the impact of the urgency at which the defect should be fixed respectively.