Defect Reporting or Tracking using own template

Written by harshitajoshi2512

Defect Tracking Using own Template –

Since there is no problem in managing the defect in some doc like Excel, but some time it becomes problematic to manage all defect with the proper status and track them time to time if the system or Defect count is huge.
But If the product is small and simple than there is no problem in using the own excel template and managing it as well.It can be done by simply creating an excel and setting the required parameters to be set or define for the defect reporting.

It depends on project as well as on organisation that what

  • Specifically they need to raise a defect
  • Kind of parameter they want to choose for defect reporting

Few standard and must required parameters are listed below for a good defect reporting or a tracking system –

  1. Defect ID
  2. Defect Description/Name
  3. Steps to Reproduce
  4. Expected Result
  5. Actual Result
  6. Defect Area
  7. Build Version  details
  8. OS and other Environment specific details
  9. Priority
  10. Severity
  11. Created by
  12. Created Date
  13. Assigned to
  14. Resolved Date
  15. Resolved By
  16. Status
  17. Comments
  18. Attachment (If required)
  19. Snapshot of Defect outcome

Create an excel and attach snapshot or description with field parameters –

  • Defect ID – A unique ID , a number for defect identification as well as for count
  • Defect Description/Name – A short definition of defect
  • Steps to Reproduce – A detailed description of defect, All steps needed to generate the defect with the setup needed
  • Expected Result – What should be the expected outcome of performing the action or functionality in which the defect is found
  • Actual Result – What is the result observed while performing the functionality or intended test case
  • Defect Area – In which area of application or project the defect identified
  • Build Version details – In which version or specific build the bug is identified
  • OS and other Environment specific details –  What was the configuration and OS of the machine on which the defect is identified
  • Priority – Order for defect resolution
  • Severity – Impact of defect on system/Application/Software
  • Created by – Name of the person who identified the bug
  • Created Date –  The date when Bug is identified
  • Assigned to – Name of the person/Team to whom defect is going to be assign
  • Resolved Date – Date when the Defect is resolved
  • Resolved By – Name of the person who resolved or fixed the defect
  • Status – Stage or status of the Bug
  • Comments – Any comments required related to defect
  • Attachment (If required) – Any file which needs to upload for reference or a required document to complete the steps for reproducing the bug
  • Snapshot of Defect outcome – The output of the Bug while performing the steps or a video can be added as per the requirement

 

 

Leave a comment