What should be done after a bug is found?
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Bug Report @ OneStopTesting
Forum Discription: After Creating the Test Plan, Writing the Test Cases and using them, Finally We need to generate those Bug Reports which Proves that Testers are Good enough & most importantly Indispensable.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=3070
Printed Date: 25Nov2024 at 7:50pm
Topic: What should be done after a bug is found?
Posted By: Sujata
Subject: What should be done after a bug is found?
Date Posted: 20Oct2007 at 12:04am
What should be done after a bug is found?
The
bug needs to be communicated and assigned to developers that can fix
it. After the problem is resolved, fixes should be re-tested, and
determinations made regarding requirements for regression testing to
check that fixes didn't create problems elsewhere. If a
problem-tracking system is in place, it should encapsulate these
processes. A variety of commercial problem-tracking/management software
tools are available (see the 'Tools' section for web resources with
listings of such tools). The following are items to consider in the
tracking process:
•Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary.
•Bug identifier (number, ID, etc.)
•Current bug status (e.g., 'Released for Retest', 'New', etc.)
•The application name or identifier and version
•The function, module, feature, object, screen, etc. where the bug occurred
•Environment specifics, system, platform, relevant hardware specifics
•Test case name/number/identifier
•One-line bug description
•Full bug description
•Description
of steps needed to reproduce the bug if not covered by a test case or
if the developer doesn't have easy access to the test case/test
script/test tool
•Names and/or descriptions of file/data/messages/etc. used in test
•File
excerpts/error messages/log file excerpts/screen shots/test tool logs
that would be helpful in finding the cause of the problem
•Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common)
•Was the bug reproducible?
•Tester name
•Test date
•Bug reporting date
•Name of developer/group/organization the problem is assigned to
•Description of problem cause
•Description of fix
•Code section/file/module/class/method that was fixed
•Date of fix
•Application version that contains the fix
•Tester responsible for retest
•Retest date
•Retest results
•Tester responsible for regression tests
•Regression testing results
A
reporting or tracking process should enable notification of appropriate
personnel at various stages. For instance, testers need to know when
retesting is needed, developers need to know when bugs are found and
how to get the needed information, and reporting/summary capabilities
are needed for managers
|
Replies:
Posted By: prakashyste
Date Posted: 16Nov2007 at 2:56am
|
Hi sujata.
Good information
|
Posted By: santoshsapkal
Date Posted: 19May2008 at 5:21am
|
Tester has to provide sufficient information so that bug should be reproduced. Thats how developer will got to know, what is actually bug is.
|
|