Print Page | Close Window

What should be done after a bug is found? Printed From: One Stop Testing Category: Quality Assurance @ OneStopTesting Forum Name: Defect Management@ OneStopTesting Forum Discription: Defect is the worst Nightmare of any Testing Engineer and is basically the elimination of bugs in software and flaws in hardware. URL: http://forum.onestoptesting.com/forum_posts.asp?TID=727 Printed Date: 29Apr2024 at 9:25am Topic: What should be done after a bug is found? Posted By: appurva Subject: What should be done after a bug is found? Date Posted: 09Apr2007 at 9:37pm 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 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 http://www.onestopfaqs.com/faqs/1613/# -

Print Page | Close Window