Defect life wheel or põrnikas life wheel is a really of import point, each in addition to every tester should know nigh it. Main target of tester is non exclusively detect the bug/ defect inward the software but also also proceed the rail of that põrnikas till its closer. So põrnikas life wheel is a life wheel of põrnikas from its rootage to its closer. Origin signal is when tester detect a põrnikas in addition to closer or closing signal is when tester re-retest in addition to unopen it.
Below shown diagram is a the Bug life Cycle.
See how põrnikas goes through a give away of phases inward his entire life. We are going to beak over each stage i yesteryear one.
NEW :
When tester execute its examination cases in addition to output of that examination illustration is non every bit expected in addition to hence tester tin say he has got a bug. Means a variance betwixt the expected effect in addition to actual effect is called bug. So the tester necessitate to instruct cook this põrnikas but he cant cook that põrnikas yesteryear himself, developer necessitate to cook this. But produce tester straight instruct to developer in addition to tell them ? similar hello developer I works life the bug, cook this soon. The answer is no. Tester necessitate to submit this põrnikas to his Team Lead showtime in addition to squad Pb volition assign the developer to cook the põrnikas later his analysis.
Important : when tester finds a põrnikas in addition to hence it is inward NEW state.
OPEN :
Once the põrnikas is submitted yesteryear the tester them squad leads piece of occupation instruct started. Team Pb necessitate to verify the submitted bug. Team Pb necessitate to produce around entry checks, you lot volition instruct a sentiment yesteryear looking below image.
Following actions necessitate to performed yesteryear the squad lead.
REJECTED:
The põrnikas is marked every bit a rejected when that põrnikas is invalid. Meaning of invalid is, around fourth dimension tester may misunderstood the functionality in addition to tin grade characteristic every bit a bug, inward that illustration that põrnikas is rejected yesteryear squad Pb later evaluation.
Important: when tester written report a põrnikas but which is a characteristic of software in addition to hence squad Pb grade it every bit rejected.
DUPLICATE :
If põrnikas is a valid põrnikas in addition to hence squad Pb volition cheque whether that põrnikas is already reported yesteryear other tester or not. If it is reported yesteryear other tester in addition to hence squad Pb grade it every bit DUPLICATE. If that põrnikas is non reported yesteryear other tester in addition to hence squad Pb aspect for scope.
As nosotros know, nosotros are working inward a team. There is a chances that the same software or same module is assigned to to a greater extent than than i tester, inward that illustration similar põrnikas tin survive works life yesteryear many tester. So squad Pb necessitate to ensure that, same põrnikas should non instruct reported twice or may survive to a greater extent than than that.
Important: if same põrnikas is reported yesteryear 2 or to a greater extent than tester in addition to hence minute reported põrnikas is marked every bit DUPLICATE.
DEFERRED:
If that põrnikas is non a duplicate põrnikas in addition to hence squad Pb volition cheque that põrnikas for DEFERRED status.
If the põrnikas is non a percentage of electrical current loose in addition to hence that põrnikas tin survive marked every bit deferred. Means suppose you lot are working inward agile methodology in addition to they bring divided the projection requirement into a small-scale builds which are called sprints, say they divided the projection requirements into the 10 sprints, similar sprint 1, sprint 2…..up to the 10 sprint. And currently you lot are working on sprint 1 but the põrnikas you lot bring works life is related to the hereafter sprints say it related to the sprint 2. but the side yesteryear side loose is for sprint 1. inward such a scenario squad Pb grade that põrnikas every bit DEFERRED. DEFERRED põrnikas is a põrnikas but it necessitate to resolve inward hereafter release.
Important: when a põrnikas is a percentage of hereafter loose in addition to hence it is marked every bit DIFERRED.
ASSIGNED:
When that raised põrnikas is valid, unique in addition to percentage of electrical current loose in addition to hence squad Pb assign that põrnikas to developer.
FIX:
Here developer start working on põrnikas to cook it. Developer brand proper changes to cook the change. And brand available that alter for testing.
RE-TESTING:
After fixing of the põrnikas that feature/functionality is available for the testing, hither tester executes those failed examination cases in addition to verify forthwith that characteristic is producing proper output or not.
CLOSED:
When that põrnikas is fixed in addition to re-tested in addition to works life working fine in addition to hence tester grade it every bit close.
RE-OPENED:
There are 2 province of affairs In which nosotros necessitate to re-open the bug.
Situation1: when developer cook the põrnikas in addition to tester re-test it in addition to later re-testing if same põrnikas is introduce or developer said he fixed the põrnikas but notwithstanding same põrnikas is introduce in addition to hence tester re-open the põrnikas in addition to i time again assign that põrnikas to developer for fixing.
Situation2: at that spot are around cases where the fixed bugs are i time again appears, inward that province of affairs nosotros necessitate to re-open that closed põrnikas in addition to assign it to the developer again.
So this is all nigh põrnikas life cycle, you lot may detect dissimilar põrnikas life wheel diagram on dissimilar resources but this i is slow to explicate i time you lot sympathise the diagram.