Skip to main content

Bug Life Cycle

Bug life cycle is a cycle of a Bug from when it is generated to when it is closed. Following phases of Bug life Cycle

  • New: When QA team find a new bug we provide 'New' status for that Bug.
  • Open: When QA team add that Bug and Team lead approve the bug to genuine then status of that bug is 'OPEN'
  • Assign: When any bug assign to the Developer then status change to 'Assign'.
  • Rejected: When developer found that bug is not genuine and he/she unable to reproduce the bug then developer change the status to 'Rejected'.
  • Deferred: When developer found that bugs is not related to current work and will be consider in later modules then developer change the status of bug to 'Deferred'.
  • Test: Once the developer fix the bug and assign to the QA team then QA team need to retest the bug to verified that the issue has been fix on not. 'Test' status means bug has been fixed and assign beck to Testing team.
  • Reopened: If QA team found that issue still not been fixed then QA team change the status to 'Reopened' and again assign to the developer team.
  • Verified: If QA Team found that issue has been fix now and testing team verified the issue and ensure that issue will not be generated in future , QA team change the status to 'Verified'.
  • Closed: After verified by QA team to ensure issue has been fix they change the status to 'Closed'. This status means bug has been tested , verified and approved.


Bug Life Cycle, Software Testing Help, Manual Testing, Testing, QA, QC
Image Source Google

Labels:
Location: Jaipur, Rajasthan, India

Comments

Post a Comment

Popular posts from this blog

Why Jmeter is best option for Performance Testing?

There are multiple tools in market for performance testing of any software but Jmeter is the best solution among all of them due to some reason listed below 1) Jmeter is the open source application so users who use this application will not to pay anything. 2) You can use Jmeter for performance of any web application,  Databases and Web Services (REST and SOAP APIs). 3) Jmeter have the user friendly UI component so it is very easy to use. 4) Jmeter can be used to simulate to put maximum number of concurrent users on a server, network or object to test its strength or to analyze overall performance under different load types. 5) Jmeter also use for functional testing for static( JavaScript and HTML) and dynamic( JSP, Servlets and AJAX) resources. 6) Jmeter provides Verity of graphical representations for performance report so it is easy to understand.
Post a Comment
Read more

How You Can Test Database?

Now we know the Database Testing which you can learn in my last article. In this article we will discuss about the steps that need to following to test any Database. Database Tester should have some basic knowledge regarding SQL Command like DDL (create/drop),  DML (Insert/Delete/Update) and DCL (Grant/Revoke).
Post a Comment
Read more

Record and Play Back in JMeter

In this section we will discuss about how to record a Test script than how we can play back that script in the browser. First we develop a  a Test Script than put a load of suppose 100 users and than run the test script again with this load while Test executing than we are getting result in performance matrices that how the Test performing in different number of users.
Post a Comment
Read more