Defect/ Bug Life Cycle
Defect life cycle also known as bug life cycle. Defect life cycle/ Bug life cycle is the journey of bug from initiation to closure during its life time. It may different from organization to organization and may project to project.
Business Analyst/ Scrum Master will monitor till closure of the defect, it may different from organization to organization.
New : During testing of the application if tester find/observed any issue then tester will raise the issue(Bug/Defect)
Assigned : Once tested raised the defect it will be assigned to the development team to fix/resolve the defect.
Open : Development team will open the defect.
Review : Development team will review the defect, whether it is genuine issue or not.
Rejected : If development team feels it is not a genuine defect then they can reject the ticket with mention their comments.
Deferred – When a defect cannot be addressed in this cycle then it is deferred to future release.
Duplicate: Development team will mark as a duplicate if it is duplicate defect means which is already raised previously.
Fixed : If development team identifies as it is genuine bug then team will fix the issue. In some organizations once, developer fixed the code development manager/team lead will review the code, whether it is impacting any other functionality or not. And they fixed the issue again they will assign to testing team for testing.
Retest : Testing team will test the defect which is assigned by development team.
Close : If testing team feels defect is resolved then they will close the defect ticket.
Reopen : If testing team feels still issue/defect not resolved then again they will reopen the ticket and assign back to development team to resolve the issue, again same cycle will follow.
I hope it helped you to understand Defect Management Life Cycle
Defect/Bug Life Cycle in Software Testing
20
638
20
70
Business Analyst , Functional Consultant, Provide Training on Business Analysis and SDLC Methodologies.
An impressive share, I simply given this onto a colleague who was doing a little analysis on this. And he in truth bought me breakfast as a result of I discovered it for him.. smile. So let me reword that: Thnx for the deal with! However yeah Thnkx for spending the time to discuss this, I feel strongly about it and love studying extra on this topic. If doable, as you develop into expertise, would you mind updating your blog with extra details? It’s highly helpful for me. Massive thumb up for this weblog publish!
What’s Taking place i am new to this, I stumbled upon this I’ve discovered It absolutely useful and it has helped me out loads. I’m hoping to contribute & aid different users like its helped me. Good job.
I went over this web site and I conceive you have a lot of great information, bookmarked (:.
really such a wonderful information
good one
Your article helped me a lot, is there any more related content? Thanks! https://www.binance.com/bg/register?ref=53551167
Thank you for your sharing. I am worried that I lack creative ideas. It is your article that makes me full of hope. Thank you. But, I have a question, can you help me? https://accounts.binance.com/id/register-person?ref=UM6SMJM3
Bug Life Cycle / What is Defect Life Cycle ? » BACareers, The Business Analyst Blog
vbmqtwjqg http://www.gu99y76qz754jhwo8t59s22et3y76yv4s.org/
[url=http://www.gu99y76qz754jhwo8t59s22et3y76yv4s.org/]uvbmqtwjqg[/url]
avbmqtwjqg
Your point of view caught my eye and was very interesting. Thanks. I have a question for you.
Thank You.
Can you be more specific about the content of your article? After reading it, I still have some doubts. Hope you can help me.
Can you be more specific about the content of your article? After reading it, I still have some doubts. Hope you can help me.