Bug Reports That Make Sense

[article]
Share URL
 
Summary:

After a defect has been found, it must be reported to development so that it can be fixed. Much has been written about identifying defects and reproducing them--but very little has been done to explain the reporting process and what developers really need. This paper is to provide a guideline for what information should be included in a report and how the information will vary based on the type of bug and the type of function.

After a defect has been found, it must be reported to development so that it can be fixed. Much has been written about identifying defects and reproducing them--but very little has been done to explain the reporting process and what developers really need. This paper is to provide a guideline for what information should be included in a report and how the information will vary based on the type of bug and the type of function.

Click on the link below to download the complete paper.

File: 
Bug Reports That Make Sense.pdf

About the author

More Like This

» The Shift-Left Approach to Software Testing [article]
» “How Was This Tested?” Providing Evidence of Your Testing [article]
» Using Equivalence Partitioning and Boundary Value Analysis in Black Box Testing [article]
» 4 Strategies for a Structured QA Process [article]
» Considering User Experience when Testing Push Notifications in Messaging Apps [article]
» Using Games to Make You a Better Tester [article]
» Use the Rejected Defect Ratio to Improve Bug Reporting [article]

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.