Bug Life cycle

(Bug Life cycle) is the journey of a defect from its identification to its closure. The Life Cycle varies from organization to organization.

The different states of a bug can be summarized as follows:

1. New
2. Open
3. Assign
4. Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed

Description of Various Stages:

New: Tester finds a defect and posts it with the status NEW. This means that the bug is not yet approved.
Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as “OPEN”.
Assign: Once the lead changes the state as “OPEN”, he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to “ASSIGN”.
Test: Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to “TEST”. It specifies that the bug has been fixed and is released to testing team.
Deferred: If a valid NEW or ASSIGNED defect is decided to be fixed in upcoming releases instead of the current release it is DEFERRED. This defect is ASSIGNED when the time comes.
Rejected: if Found bug is not invalid, it is DROPPED / REJECTED. Note that the specific reason for this action needs to be given.
Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “DUPLICATE”.
Verified: If the Tester / Test Lead finds that the defect is indeed fixed and is no more of any concern, it is VERIFIED.
Reopened: If the Tester finds that the ‘fixed’ bug is in fact not fixed or only partially fixed, it is reassigned to the Developer who ‘fixed’ it. A REASSIGNED/Reopen  bug needs to be COMPLETED again.
Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “CLOSED”. This state means that the bug is fixed, tested and approved.

Comments

Post a Comment

Popular posts from this blog

Online Selenium Training With Real Time Scenario

SELENIUM TRAINING COURSE CONTENT Introduction ü What is automation testing ü When to go for automation ü Different automation tools (vendor & open source tools) ü Advantages of  automation ü Difference between manual testing & Automation testing process                                     Introduction to selenium ü What is selenium Tool ü Use of selenium tool in automation ü Features of selenium tool ü Differences  between selenium and other tools Selenium Components ü Selenium IDE ü Selenium RC ü Selenium WebDriver ü Selenium  Grid Configuration of selenium IDE & Dev. Scripts ü Installing/Downloading Selenium IDE ü Features of Selenium IDE ü Recording/Creating your first test with Selenium IDE ü Script Debugging in Selenium IDE. ü How to save recorded script ü Running the script ü Selenium Action Commands ü Assert ü Verify ü Adding Selenium IDE comments ü Synchronization commands ü
Continue Reading »

Online Tricentis Tosca Automation Training with Real Time Scenarios

ONLINE TRICENTIS TOSCA AUTOMATION TRAINING WITH REAL TIME SCENARIOS TOSCA COURSE CONTENT (40 Hours) Tosca has become an leading Automation tool in market migrating most of the existing projects to tosca, which has an excellent flexibility to handle script-free automation tool. This training helps the team to write complex/simple automation scripts very easily and can able to handle any type of scenarios. Here with providing the list of topics covered under this course: Tosca Introduction  (Duration 2 Hours) Brief about Tricentis Tosca Testsuite Overview and concept Business dynamic TestCases and test automation System Requirements for Tricentis Tosca Testsuite Installing Tosca Installation process Unattended installation  License administration Node Locked License Floating License Commuter License Cloud License Specific License Files and directories Maintaining the Tosca installation (Duration 2 Hours) Working Features in TOSCA The Menu Object
Continue Reading »

Online Training for Manual/Functional

MANUAL TESTING CONCEPTS Introduction to Software Testing ü   What is software Testing ü   Why Software Testing ü   Benefits of Software Testing ü   Who will do the Software Testing ü   What is Quality ü   What is Defect ü   Project Vs Product   Software Development Life Cycle (SDLC) ü   What is Software Development Life Cycle ü   Why Software Development Life Cycle ü   Phases of Software Development Life Cycle ü   Initial ü   Analysis ü   Design ü   Coding ü   Testing ü   Delivery & Maintenance Software Development Life Cycle (SDLC ) Models ü   Water fall model ü   Vmodel ü   Prototype Model ü   Agile Model with Scrum Method  Software Testing Methodologies ü   Block box Testing ü   What is Block Box Testing ü   Who will Perform Block Box Testing ü   How to Perform Block Box Testing ü   Block Box Testing Techniques White Box Testing ü   What is White Box Testing ü   Who will Perform Block Box Testing ü   H
Continue Reading »