In Last article, nosotros withdraw maintain seen that how põrnikas tin endure arise piece developing a software. Now inwards this article, nosotros volition discus near ‘Bug Life Cycle’. Bug life wheel starts when põrnikas volition endure arise inwards software testing phase. After completing 1 cycle, nosotros may insure that posted põrnikas volition non endure re-produced again. Bug volition withdraw maintain dissimilar condition inwards põrnikas life cycle. We volition encounter this inwards detail.
Below are the steps for põrnikas life cycle.
- New
- Assigned
- Open
- Fixed
- In progress to QA
- Retest
- Verified
- Closed
- Duplicate
- Reopen
- Rejected
- Not a Bug
This all are the dissimilar stages of põrnikas life cycle. Now nosotros volition sympathise near each of them. Lets accept 1 past times 1 declination.
- New : As nosotros know this is the fist stage of põrnikas life cycle. When põrnikas arise, a tester withdraw maintain to postal service a bug, at that fourth dimension its condition is grade every bit ‘New’.
- Assigned : As nosotros withdraw maintain know that at that topographic point are dissimilar form of põrnikas tin endure arise inwards application similar UI, Functional, Integration, database related etc. When põrnikas is arise, Pb needs to approve the same hence it may assign to respected developer squad to solve. Thus, When defect is assigned to the associate developer hence that põrnikas volition grade every bit assigned condition in addition to assigner yell volition endure displayed there. For to a greater extent than specification nosotros tin grade this condition every bit ‘Assign to Developer’.
- Open : This condition volition endure marked when developer has been started working on põrnikas but it withdraw maintain non been resolved yet. It way that põrnikas is approved in addition to it needs to solved at that fourth dimension condition of põrnikas is ‘Open’.
- Fixed : This condition volition endure marked when põrnikas volition endure resolved past times developer squad in addition to assign to a tester to verify the bug. Code changes in addition to Unit testing withdraw maintain been done past times developer squad hence it tin endure assigned dorsum to the testers squad in addition to they withdraw maintain to showtime verify the põrnikas subsequently fixing the põrnikas only. For to a greater extent than specification nosotros tin grade this condition every bit ‘Release to QA’.
- In Progress to QA: This condition tin endure assigned when developer withdraw maintain resolved the põrnikas but it is pending from tester side. Here when tester volition showtime on working the põrnikas at that fourth dimension they tin assign ‘In Progress To QA’ condition hence tester leader tin recognize that how many bugs are at that topographic point inwards progress or nether working status.
- Reset : This condition tin endure assigned when roughly code changes withdraw maintain been assigned to a tester but that code changes volition non run in addition to põrnikas is reproduced 1 time to a greater extent than hence this condition is assigned to the bug.
- Verified : When põrnikas is verified past times testers in addition to it volition endure ensured that põrnikas volition non endure reproduced 1 time to a greater extent than inwards software hence tester tin endure grade that põrnikas every bit ‘Verified’. Once põrnikas volition endure assigned every bit verified it way all integration amongst software likewise verified in addition to põrnikas withdraw maintain been fixed properly in addition to it volition non touching on inwards whatever other purpose of software every bit well.
- Closed : If põrnikas volition non be for long fourth dimension inwards the software in addition to põrnikas withdraw maintain been verified past times a tester hence that põrnikas tin endure grade every bit ‘Closed’.
- Duplicate : When at that topographic point are huge application in addition to to a greater extent than than 1 tester volition run together at that fourth dimension it may possible that põrnikas withdraw maintain been posted twice. At that fourth dimension if developer feels that põrnikas is duplicate hence they tin grade it every bit ‘Duplicate’. Here they needs to lift roughly other ticket divulge which is same.
- Reopen : This condition withdraw maintain been assigned when a tester expire that põrnikas inwards software 1 time to a greater extent than in addition to it is non resolved properly. When põrnikas is reproduced inwards software hence a tester tin ‘Reopen’ the bug. Thus, developer squad withdraw maintain to run on it 1 time to a greater extent than in addition to 1 time to a greater extent than ask to fixed it.
- Rejected : This condition withdraw maintain been assigned to a põrnikas when developer squad feels that the posted põrnikas is non genuine hence the condition of põrnikas volition endure changed every bit ‘Rejected’.
- Not a Bug : Not a põrnikas way If subsequently delivering the production If customer enquire for small-scale changed for hold off in addition to fill upwards hence it volition non endure considered every bit bug. It must endure marked every bit ‘Not a Bug’ condition but it must endure resolved in addition to tested every bit per the novel requirement of the client.
This all are the dissimilar condition of software põrnikas cycle. Once the ‘Closed’ condition withdraw maintain been assigned to a põrnikas hence it volition endure the terminate of the bug.