Bug Reports That Make Sense

[article]
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.

About the author

Mary Decker's picture Mary Decker

Mary Decker is a software developer/test engineer with seventeen years of experience. She has worked as a consultant to several Fortune 500 companies, providing computer/systems analysis and support while developing several customized tracking systems. She has also done consulting work for the government providing analytical database systems, budget modeling systems and support. Currently, she is working on a Windows cost accounting package designed for Government Contractors where she is working both as a developer and as the director of testing. Mary has attended the University of Maryland and received her degree from Montgomery College.

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Oct 12
Oct 15
Nov 09
Nov 09