explain bug life cycle
- 7 Answers
- 19067 Views
- Polaris, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
the following steps we follow in the bug life cycle.
1)execute the test, compare the actual result with the
documented expected result.if any discepancy exist, log the
discrepancy with the status as NEW.
2)tester/testleader(depends upon the company) OPEN that
one and review with the developer about discrepancy.
3)if it truly a discrepancy developer rectify that one and
update its status to FIXED.
4)it is routed back to the tester for regression testing
5)tester retest that one and compare the actual result with
the expected result.both are same he close the defect and
update its status to CLOSED.
6)if it is not corrected tester assign it to the developer
and update its status to RE-OPEN.
| Is This Answer Correct ? | 25 Yes | 2 No |
Answer / kommineni
While testing if we found any mismatch between the Expected result and Actual result we called this mismatch as Defect
Once we got a defect we have to gave the status to that defect as New and we have to assign that defect to the concerned developer and if the developer accepts the defect he will give the status as Open to tat defect if he is not agree with ur defect he will gives the status as Reject If he agree with ur defect then he is the responsible person to fix the defect
Once he fixed the defect he will give the status as Fixed
and he re-assigned that defect to testing people
Then we are going to conduct the retesting on the defect to validate whether the defect is fixed correctly or not
After this re-testing we are conducting the Regresiion testing on the total build
Developer might alter any of the code in the build to fix this defect so we are conducting regression testing on the total build.
If we got any defect in Regression testing we have to raise the defect with status NEW
If we found the defect is not fixed properly in re-testing we have to give the status as Re-Open to the defect and we are re-assigning the defect to the same developer
After conducting the retesting and regression testing we are giving the status as Closed
This is complete real time scenario of BUG life cycle..
Suppose If we raised a defect to the developer he will get a auto generated mail from Quality center about the defect
This mail will goes for two persons one is author and the second person is to whom you assigned the defect......
| Is This Answer Correct ? | 8 Yes | 2 No |
The duration or time span between the first time bug is
found (‘New’) and closed successfully (status: ‘Closed’),
rejected, postponed or deferred is called as ‘Bug/Error
Life Cycle’.
(Right from the first time any bug is detected till the
point when the bug is fixed and closed, it is assigned to
various statuses which are New, Open, Postpone, Pending
Retest, Retest, Pending Reject, Reject, Deferred, and
Closed.
There are seven different life cycles that a bug can passes
through:
< I > Cycle I:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) Test lead finds that the bug is not valid and the bug
is ‘Rejected’.
< II > Cycle II:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is invalid and is marked with a status
of ‘Pending Reject’ before passing it back to the testing
team.
5) After getting a satisfactory reply from the development
side, the test leader marks the bug as ‘Rejected’.
< III > Cycle III:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug
as ‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug
to ‘Pending Retest’ and passes on to the testing team for
retest.
7) The test leader changes the status of the bug
to ‘Retest’ and passes it to a tester for retest.
8) The tester retests the bug and it is working fine, so
the tester closes the bug and marks it as ‘Closed’.
< IV > Cycle IV:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug
as ‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug
to ‘Pending Retest’ and passes on to the testing team for
retest.
7) The test leader changes the status of the bug
to ‘Retest’ and passes it to a tester for retest.
8) The tester retests the bug and the same problem
persists, so the tester after confirmation from test leader
reopens the bug and marks it with ‘Reopen’ status. And the
bug is passed back to the development team for fixing.
< V > Cycle V:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The developer tries to verify if the bug is valid but
fails in replicate the same scenario as was at the time of
testing, but fails in that and asks for help from testing
team.
5) The tester also fails to re-generate the scenario in
which the bug was found. And developer rejects the bug
marking it ‘Rejected’.
< VI > Cycle VI:
1) After confirmation that the data is unavailable or
certain functionality is unavailable, the solution and
retest of the bug is postponed for indefinite time and it
is marked as ‘Postponed’.
< VII > Cycle VII:
1) if the bug does not stand importance and can be/needed
to be postponed, then it is given a status as ‘Deferred’.
This way, any bug that is found ends up with a status of
Closed, Rejected, Deferred or Postponed.
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / pinki
The following are the phases of a Bug/Defect Life cycle-
1)Opening of new bug
2)Acceptance of the bug
3)Pending state
4)Fixed stage
5)Closd Stage
6)Re-open stage
| Is This Answer Correct ? | 7 Yes | 5 No |
Answer / mfsi_chinmayb`
Hi
1)After a test is executed if the behavior deviates from the
actual one then the corresponding bug or defect is tagged as
NEW .
2) Then it is now the job of the tester to OPEN it up with
the developers.
3)Then it is FIXED by the developers.
4)Then again it is retested or it undergoes regression testing.
5)If it is fixed fixed then the bug is CLOSED
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / shilpa churi
1) Tester find the bug.
2) Tester enter bug in Bug life cycle / Defect life cycle
and pur status as "OPEN".
3) Tester inform concern developer regarding "OPEN" status
bug.
4) Developer resolve the bug and change status as "Resolve".
5) Tester retest and if it re-occure than put status as "Re-
OPEN".
6) If it is fix than change status as "Close".
| Is This Answer Correct ? | 4 Yes | 5 No |
Answer / srikar.k
Raise defect
Internal review
<---submit to deceloper--->
post poned rejected
accepted
fixed
<--retest-->
yes No --------->go to same process
closed
| Is This Answer Correct ? | 5 Yes | 15 No |
How will you go with testing process if only project requirements document is given to you
a apllication is given to you but the requirements and functionalities are missing what will you do to start the testing?
What disabilities are affect on software usability?
in the account there is 10,000 rupees and i entered 20000, in this case how will you test the application
what is the combination of grey box testing
What is the negative test cases for www.yahoo.com?
What is the initial stage of testing?
What is data flow diagram?
What is the difference between use case and test case? give example.
what is Beta testing??
what is test plan and what it consists?
15 Answers AndPlus, Forum, MBT, TCS,
what is the diffn betn web based application and client server application
Automation Testing 
