When a bug is found, it needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested. Additionally, determinations should be made regarding requirements, software, hardware, safety impact, etc., for regression testing to check the fixes didn't create other problems elsewhere. If a problem-tracking system is in place, it should encapsulate these determinations. A variety of commercial, problem-tracking/management software tools are available. These tools, with the detailed input of software test engineers, will give the team complete information so developers can understand the bug, get an idea of its severity, reproduce it and fix it.
What should be done after a bug is found ?
Labels: bug lifecycle, cause of bugs, software bugs, software testing
Posted by Rajeev Prabhakaran
Subscribe to:
Post Comments (Atom)
Archives
Recently Added
May i help you ? What are you searching for ?
Tags
- axioms. testing (1)
- black box (1)
- Boundary Value Testing (1)
- bug (3)
- bug lifecycle (2)
- bugs (1)
- cause of bugs (2)
- cm tools (1)
- Comparison Testing (1)
- Conditional Testing (1)
- configuration management (1)
- configuration management tools (1)
- Data Flow Testing (1)
- defect (1)
- Different types of testing (1)
- errors (1)
- Extensive testing (1)
- G11N (1)
- Globalization (1)
- Globalization (G11N) (1)
- Globalization G11N (1)
- Good code (1)
- Good Design (1)
- Graph Based Testing (1)
- Gray Box (1)
- I18N (2)
- I18N and L10N (2)
- Inspection (1)
- Internationalization (2)
- Internationalization (I18N) (1)
- L10N (2)
- Localization (4)
- Localization (L10N) (4)
- Localization Testing (1)
- Loop testing (1)
- major bugs (1)
- major errors (2)
- methods of testing (1)
- Project (2)
- QA (3)
- Quality (1)
- Quality assuarance (4)
- quality control (2)
- Requirements (1)
- Roles and responsibilities (1)
- SDLC (1)
- software bugs (4)
- software developement life cycle (2)
- software developement process (1)
- Software Development (4)
- software failure (1)
- software process (1)
- Software requirement specifications (1)
- Software Requirements (1)
- software testing (13)
- Software testing process (1)
- software verification (1)
- SRS (2)
- System requirement specification (1)
- system testing (1)
- Test Cases (2)
- Test Management (1)
- Test Plan (2)
- testers (2)
- testing (3)
- testing methods (1)
- Testing Standards (1)
- testing techniques (1)
- Types of testing (1)
- UAT (1)
- user acceptance testing (1)
- validation (1)
- verification (1)
- verification and validation (1)
- Walk through code (1)
- Walk-through (1)
- what is walk through (1)
- white box (1)

0 comments:
Post a Comment