Bug Life Cycle

Bug Life Cycle

During the test execution process whenever the functionality doesn’t work according to requirement, it is known as Bug/Defeat.

This Bug has to go through a specific life cycle known as Bug/Defeat life cycle.

Bug life Cycle talks about the complete cycle of a bug right from the stage it is found, fixed, retested and close. It has a various status like new/open, assigned, fixed, close, reopen.

Bug Life Cycle

  • New/Open: As soon as we find a bug, the status of the bug changed to new/open.
  • Assigned: This bug is reported to the concerned person by changing the status to assigned.
  • Fixed: The developer first go through the bug and check if it is valid or not and if it is a valid bug then test engineer starts reproducing the bug in the application according to the steps mentioned in the bug report.
  • Close/Reopen: After the bug is fixed it is handed over to the test engineer for re-testing process and during this process, if we found that bug is fixed properly then the status is changed to close else if the bug still exists then the status is made as Re-open and assigned back once again to the developer.

This process continues until the bug is fixed and close.

NOTE: When we find a bug and developer fix it, we do one round of Re-testing.

During this process, if the bug is fixed properly then this status is close and because of the code changes, any other bug found the status is new.

During Re-testing process, if the bug is not fixed properly then the status is Re-open and any other bug is found due to code changes status is new.

NOTE: whenever a bug is fixed and code changes are done along with retesting of the bug we also do one round impact area changing if required (depends upon modules).

Every bug found we always prepare a separate bug report so that it becomes easy for login and tracking the bug.

OTHER STATUS

  • INVALIDInvalid status is given by developer when he found that this is not a bug actually. It may happen due to Test engineer misunderstanding or developer misunderstanding requirement.
  • Duplicate: If the same bug is log/report to the developer in multiple times is known as duplicate. Here the question is why duplicate?

then the answer is due to common modules or dependent modules.

How to avoid duplicates bug?

As soon as find the bug, search bug repository

  • If bug exists, do not log/report
  • If bug doesn’t exist

log Bug and store in Bug repository , send it to developer

NOTE: searching in bug repositories always a time-consuming in common modules or dependent modules.

  • Inconsistent Bug: Some time it is happening or seen and sometimes it is not happening so the best option is to take screenshots and sent to the developer.
  • Can’t Fix: All can’t fix bugs are minor bug but all minor bug is not can’t fix. It is found in the core of code and it is the mistake of architecture, not a developer and test engineer and there is no technical support.
  • Differed/post/pone: It is a minor bug which is post one to the next release. When there is not next release, we will fix in maintained.
  • Request For Enhancement: It is a suggestion and requirement review is the best option.
  • Not Reproducible: Developer accept the bug but not able to find the same issue after following the navigation step mention in the bug report.

 

 

Spread the love

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top