Defect Life Cycle

 

“Never allow the same bug to bite you twice.” (Steve Maguire)



A defect lifecycle is the movement of a defect or bug through different phases from the beginning when it was identified till it is verified and closed.


There are different tools used for managing the defect currently (Jira, Bugzilla, HP ALM, etc.). Different organizations follow different processes for managing the defect, however underlying phases remain the same.







New

It is the phase when the defect/bug is identified. As soon as a defect is found it is assigned with 'New' state and the process of defect life cycle starts. 


Open

From the 'New' state the defect moves to the 'Open' state where the defect is assigned to dedicated developer who first tries to recreate the defect, if the defect is valid then the developer starts fixing the bug. During this phase if the defect is not valid then it moved to a deferred state.


Deferred

This state occurs when the defect is not appropriate, then the developer can move the defect to this stage.


Fixed

Once the defect working stage is completed by the developer moves the defect state to 'Fixed', developer also assigns the defect to the respective QA member for further testing.


Retest

In this phase, the defect is tested by the respective QA member, and based on the testing the defect is moved to the next valid phase. If the testing is successful without any issue tester moves the defect to the 'Closed' phase. If the defect occurs again or breaking any other functionality then the defect is moved to the 'Reopen' state.


Reopen

Once the defect is reopened again the cyclic process starts again with assigning the defect to the developer and the cycle continues till the defect is successfully tested.


Closed

When the defect is tested/verified successfully, then this phase is the closure of the defect and the last phase of the defect life cycle.

However if in near future the same defect is found then this defect can be reopened and the cycle continues.



The above defect life cycle is a reference, many organizations have their own implementation of the life cycle with different phases. 












Comments

Post a Comment

Popular posts from this blog

Get first non-repeating Letter

import java.util.HashMap ; import java.util.LinkedHashMap ; import java.util.Map ; import java.util.HashMap ; import java.util.LinkedHashMap ; import java.util.Map ; public class Check { public static String firstNonRepeatingLetter ( String str) { String val= null ; char [] var =str.toCharArray(); LinkedHashMap < Character , Integer > map = new LinkedHashMap<>(); for ( int i= 0 ;i< var . length ;i++){ if ( map .containsKey( var [i])){ map .put( var [i], map .get( var [i])+ 1 );} else { map .put( var [i], 1 ); } } for ( Map . Entry < Character , Integer > entry : map .entrySet()){ if ( entry .getValue()== 1 ) { val = Character . toString ( entry .getKey()); break ; } } return val; } public static void main ( String [] args) { System . out .println( firstNonRepea...
Read more

Cypress run command

To run particular test spec file  node_modules/.bin/cypress run -s "cypress/integration/examples/Test1.js" To run all the test present under cypress folder node_modules/.bin/cypress run  To open cypress test runner UI node_modules/.bin/cypress open To execute cypress test in particular browser (by default cypress run in headless mode) node_modules/.bin/cypress run --browser {browserName}
Read more

Docker commands

List all images in docker-engine docker ps -a Delete image from the local image store docker image rm alpine:3.4 Run a container from the Alpine docker container run --name web -p 5000:80 alpine:3.9 Stop a running container through SIGTERM docker container stop web Stop a running container through SIGKILL docker container kill web List the running containers  docker container ls Print the last 100 lines of a container’s logs docker container logs --tail 100 web(container name) List the networks docker network ls   
Read more