bug life cycle

[skiran19]

It defines the Series/Process of steps followed by the time a bug is found, fixed and closed.

The Steps followed are:-

1. As soon as the bug is found it entered into the defect tracking system and assigned the status as "NEW".

2. Once its been analyzed and accepted as a geneuine- defect, the status is changed to "OPEN". If the bug is found to be invalid the status is changed to "REJECT".

3. Its then assigned to a developer status changes to "ASSIGNED TO".

4. Once its fixed by the developer status changes to "Fixed Ready to test".

5. Tester then Re-test the fix and if fix works fine, he/she set the status to "Closed".

6. In some cases, if the bug is a major fix then it is postponed to the future releases in that case the status is changed to "Deffered" an consider for future release.

[raj1402]

Bug life cycle starts when a tester finds a bug and it goes through different stage till it is closed finally by tester.

Bug life cycle:

1."new" -as soon as the tester finds the bug it is reported in defect tracking system.

2."validation by team lead". Bug found by tester is validated by team lead against various specifications, if he thinks bug is geninue, assigns to developer else marks rejected.

3."rejected"-invalid bug is marked by test lead as rejected.

4."assigned"-valid bug is assigned to developer by test lead.

5."validation by developer".bug assigned to developer is validated by developer.if the bug is geninue, bug is marked as "open" else marked ""pending rejected"

6."pending rejected"-invalid bug assigned to developer is marked as pending rejected by developer.

7."open"-valid bug assigned to developer is opened by developer to fix it.

8."fixed"-valid bug after fixed by developer is marked as fixed by developer. And marked as "pending retest" by developer lead.

9."pending retest"- fixed bug is marked as pending retest by developer lead for retesting.

10."validation by team lead"-the test fixed by developer is validated by team lead and marked as "retest".

11."retest"-tester retest the bug fixed by developer for previously raised bug.

12."validation by tester"-tester does retest and validates the bug whether it is fixed or not. If fixed the bug is closed and marked as "closed" else marked as "reopen".

13."reopen"-if the bug after retest behaves same as before or has different bug then tester marks the bug as "reopen" and sends to developer.

14."closed"-after retesting if the bug is fixed then marked as "closed".

Apart from this "BLOCKED" "POSTPONED" AND "DEFERRED" .

"BLOCKED"-when a bug reported by tester is already reported by another tester, the bug is marked as "blocked" .once the bug is fixed, it is retested.

"POSTPONED"-When the bug is postponed indefinitely due to unavailability of test case or functional requirements the bug is marked as "POSTPONED".

"DEFERRED"-When the bug reported by tester is of no importance or the bug does not have impact ,the bug is marked as"DEFERRED" and is fixed in next release.

Thanks & Regards
Raj1402

[teena_pappachan]

Very nicely explained

It defines the Series/Process of steps followed by the time a bug is found, fixed and closed.

The Steps followed are:-

1. As soon as the bug is found it entered into the defect tracking system and assigned the status as "NEW".

2. Once its been analyzed and accepted as a geneuine- defect, the status is changed to "OPEN". If the bug is found to be invalid the status is changed to "REJECT".

3. Its then assigned to a developer status changes to "ASSIGNED TO".

4. Once its fixed by the developer status changes to "Fixed Ready to test".

5. Tester then Re-test the fix and if fix works fine, he/she set the status to "Closed".

6. In some cases, if the bug is a major fix then it is postponed to the future releases in that case the status is changed to "Deffered" an consider for future release.