Defect Lifecycle



New :- When ever the tester/QA finds a bug in the software, he logs it as New bug. This is logged in any defect tracking tool that the company is using for the project.

Assigned :- The newly raised defect/bug is then assigned to a developer by the concerned team lead or manager.

Fixed :- The bug when assigned is then in progress where the developer works on it, fixes it and marks it as fixed.

Verified :- The fixed bug is verified by the tester/QA to see if it is fixed. This is known as retest.

Reopened :- If the retest is a fail, the bug is reopened and sent back to the development team.

Closed :- If the retest is a pass, the bug is closed.







5 comments:

  1. I simply wanted to write down a quick word to say thanks to you for those wonderful tips and hints you are showing on this site.… I love to read your Software QA services articles because your writing style is too good, its is very helpful for all of us and I never get bored while reading your article because, they are becomes a more and more interesting from the starting lines until the end.

    ReplyDelete
  2. Really useful post. Thanks for sharing such a interesting content with us. Keep sharing more like this post. Checkout the detailed information about security testing services and how it helps software development companies.

    ReplyDelete
  3. Really informative post about software testing strategies. Testing has many benefits and one of the most important ones is cost-effectiveness. Know more detailed information about software testing companies here.

    ReplyDelete