Software Bug Handling Process And Tools
by Nataliia Vasylyna | December 13, 2011 10:00 am
Software bug handling is a significant area of quality assurance activities.
At the time of software testing the developers who correct identified software bugs are generally not the identical as software testers who monitored and reported the errors in the first place. The exclusion is unit testing, which is often performed simultaneously to coding by the same individual.
In the majority of companies software bugs handling is implicitly assumed to be segment of the project management activities. A formalized software bug handling process distinguishes weighty activities and rules, principles, parties involved and their obligations as well. It is generally defined by the various states associated with individual bug status and transitions among these states due to status modifications.
Newly reported software bug has the “new” status, which may go through different status modifications, such as “working”, “re-verify” and other until it is “closed”. Various bug handling processes can comprise various collections of bug status and other possible characteristics.
The execution of the software bug handling process and enforcement of different related rules commonly require the support of software tools.
At the time of software testing of big software systems in IBM there are 2 bug tracking tools:
- IDSS (an IBM internal tool, were used for defect[1] tracking)
- CMVC (IBM product for configuration management and version control)
In the majority of companies different software project management tools[2] are also used for version control and bug tracking. Such tools as Bugzilla and Issuezilla are generally employed to handling bugs for medium and large open source projects.
Learn more from QATestLab
Related Posts:
- defect: https://blog.qatestlab.com/2011/10/11/main-types-of-defects-in-software-testing/
- project management tools: https://qatestlab.com/technologies/software-infrastructure/test-management-tools/
- Optimizing API Testing: Easy Scheduling with Effective Tools: https://blog.qatestlab.com/2024/06/06/optimizing-api-testing/
- No-code Solutions = No More Guarantees: https://blog.qatestlab.com/2023/01/11/no-code-solutions/
- Software Development (Doesn’t) Need Independent QA: https://blog.qatestlab.com/2024/11/14/software-development-doesnt-need-independent-qa/
Source URL: https://blog.qatestlab.com/2011/12/13/software-bug-handling-process-and-tools/