Every Software tester would have heard the word Bug or defect, Finding out this defect in the given application is the goal for the each and every software testers. In this part of the tutorial, we are going to discuss briefly about Defect Life Cycle.

If you have missed any of our previous tutorials, please check the list of the Selenium tutorials here.

Let’s start with basics;

What is a Defect/Bug?

A Defect or Bug is a term used to denote the errors occurs in the application. These defects may occur due to the mistakes are done by the programmers during the development phase. The important task of the testers is to examine the given application to find out the defects.

What is a Defect Life Cycle?

Once a defect was found by a tester, then the software development team should work on the application to fix it up. Defect Life Cycle is the process carried out by the organization in order to fix the defect found by the tester’s team.

Defect Life Cycle stages were explained briefly below,

Defect Life Cycle

Let’s start with the 1st stage of the Defect Life Cycle:


It is the first stage of the defect life cycle and this phase starts once a new bug was logged for the first time.


In this stage, once the tester logs the defect the Test lead will verify it and approves the defect and he will assign the defect to the development team. This process will also vary in two types in such as, the defect will be assigned to the developer who carried out the development part or to the Dev Lead for getting the approval of the defect and he will assign it to his team for verification.


The status of the defect will be changed to Open state once the development team starts working on it.


Fixed refers that the developers have done the necessary changes required to fix the bug and the defect is fixed. It also indicates that the testers need to work on it again to verify the fix and assure the bug is fixed.


Now the process will be clear to you, Here the testers team will reopen the defect which is moved to Fixed by the development team to verify whether the bug got fixed or not.

FREE PDF: Learn the Latest Selenium Topics


This is an important part of the Defect Life Cycle, After retesting the processed code if the trainers found the defect still exists they will reopen it again for the development team to work on it again. Hence it again moves to the 1st level of the cycle and starts from first.


The defect will be marked as deferred and the fixing process of the defect will be postponed to the next release with respect to the priority of the bug, There can be many reasons such as the bug may not majorly affect the application, no time for the fix because of the release date.


Developers can reject the bug when they feel it as not genuine, They will reject the bug and mark it as rejected.


Foot Note:

Once you are clear with the Defect Life Cycle then it is easy to understand the inside processes of testing. Our Manual + Selenium training in Chennai will help you to learn each and every concept professionally from real-time experienced software testers.

Forward us your queries to get answered by our trainers – Selenium FAQs..!

If you like to discuss with our trainers directly book your free session now +91-9884412301

Also Read:


defect life cycle | defect life cycle ppt | defect life cycle pdf | bug life cycle | selenium tutorials | free selenium tutorials | selenium tutorials for beginners