Bug Reports That Make Sense

Author: stickyminds.com
Category: Bug Reporting
Comments (0)

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. The purpose of this paper is to provide a guideline for what information should be included in a report, and how those requirements will vary based on the type of bug and the type of function.

Read More...

Sponsored Links

Read Next: Bug Tracking Basics

Comments

Bug Reporting

After the Bug Report
Bug Taxonomies
Bug Movie
Bug Counts vs. Test Coverage
Using Bug-Tracking Systems as Idea Repositories
Bug Reports That Make Sense
Bug Tracking Basics
Issue Tracking and Project Management with BUGtrack
Defect Management in Development and Test
It’s Not About the Bugs