A Guide to Evaluating a Bug Tracking System
Evaluating a bug tracking system requires that you understand how specific features, such as configurable workflow and customizable fields, relate to your requirements and your current bug tracking process. This article provides tips and guidelines for evaluating features, and explains how these features fit into a defect tracking process. Read Article... Download Article...
Bug Reports That Make Sense
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¨C-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 Article...
Communicating and Managing Bugs Efficiently
Everyone knows that it is the responsibility of the tester not only to find and report bugs, but also to manage and handle bugs efficiently until they have been fixed. How do you form an opinion about the nature of a software error and estimate the merit of that error? Though it may look easy, in reality, it is not. In this article, the author describes better ways to report bugs. Read Article...
How to Report Bugs Effectively
Anybody who has written software for public use will probably have received at least one bad bug report. Reports that say nothing ("It doesn't work!"); reports that make no sense; reports that don't give enough information; reports that give wrong information. Reports of problems that turn out to be user error; reports of problems that turn out to be the fault of somebody else's program; reports of problems that turn out to be network failures. Read Article...
How to find and implement the right system for your bug tracking needs
Defect tracking systems influence business-critical decisions. Building and installing a corporate-wide defect tracking system takes a small but well-balanced development team. Your implementation may be as simple as opening the package and typing "setup" or it may take months of programming. Here's how to find and implement the right system for your organization. Read Article...
The Importance of Bug Testing
Luke Andrews writes: "The following whitepaper discusses the importance of bug testing with respect to client and vendor environments. Various responsibilities are placed on either side of product development, and it is necessary to understand the reasons behind practicing secure coding and ethical loyalty." Read Article...
Using Bugs To Bring Developers and Testers Closer Together
Experienced software tester Michael Kelly provides some good suggestions on how testers can get and share information with developers, to improve collaboration and make better programs with less struggle. Read Article...
Using Bug-Tracking Systems as Idea Repositories
When unnecessary information is entered into bug-tracking systems, they are not as effective as they could be. In this article, Adam Kolawa outlines what type of information should be entered into a bug-tracking system during development and after code freeze, and how to use the information when designing future product versions.
Related keywords:
© 2008 www.dvdtoiphone.org All rights reserved