Interested to Buy Any Domain ? << Click Here >> for more details...
What is the bug life cycle?
- 3 Answers
- 7758 Views
- Keane India Ltd, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / rahul pandey
BUG CYCLE
1.NEW- first of all a new defect is reported by test er to his test manager.
2.Open- than that defect is opened by the test manager and the next step performed by the test manager is "REVIEW" in which he will check for three things
a.whether the defect is duplicate or not
b.whether the defect is valid or invalid
c.Deferred-it means if the defect is not much that imp.
and can be handled at next version than that defect is
set as new
3.Assigned- Now the test manager will assign that valid defect to developer for fixing it
4.Fixed-here it's developer responsibilities to fix that bug allocated by his test manager.if the test is fixed it is sent to tester for retest.
5.Retest-now the tester will retest that part only that was having defect.if that bug has been fixed than tester will close that defect if not than it will "REJECT FIX" and that will again "OPEN"
6.Closed-if the bug has been fixed tester will close it ...and after closing regression testing is being performed to check whether any change has been arrived due to testing in any unchanged product...
again bug life cycle starts
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / jhuma
A bug life cycle may be like this...........
1.new:-when the bug is first time found/revealed by the tester,he communicates with his lead to be sure about the validity of the bug.If it is valid,then it is reported and the status becomes "new"
2.Assigned:-After a bug is reported new,it comes to the development team and and the lead verifies the bug and if found valid he assigns it to a particular developer.Now the status becomes assigned.
3.open:;when a developer is assigned a bug,he opens it to work on the bug.He changes the status to "open".
4.fixed:-once the developer makes necessary changes to the code,he changes the status to "fixed".
5.retest:-then it comes to the tester for retesting.now the tester changes the status to "retest".
6.closed:-if the tester is satisfied with the changes or the fixing of the bug after retesting,he closes the bug and changes the status to "close".
reopen:-if after retesting,the tester finds any defects or wrong,he reopens the bug and changes the status to"reopen".
7.rejected:-if the developer finds the bug is invalid,he rejects the bug and changes the status to "rejected".
8.Deferred:-if the developer thinks that the bug can be fixed later because of less importance of the bug,he can defer it and now the status becomes "deferred".
| Is This Answer Correct ? | 3 Yes | 4 No |
Answer / tejasri
There are Different Stages in bug life cycle
New: When the bug is found by tester first first the status'
of the bug is "NEW".
Open: When the status is in "OPEN" This gives that the
developer is currently on the bug.
Fixed:After the bug is corrected by the developer with some
changes in the code the status of bug is "FIXED".
DEFERRED:When bug status is in "DEFERRED" it means the bug
will fix later(or) Postpone
DUPLICATE:When the status of bug is "DUPLICATE" it means
that the bug which the tester posted is same like the other bug.
REJECTED:When the bug is in "REJECTED" status then the bug
is not accepted by the developer.
CLOSED:This status"CLOSED" is posted by the tester after the
regression test is completed and if the bug is working correct.
REOPEN: This status "REOPEN" is posted when after regression
test if the defect is still exist.
| Is This Answer Correct ? | 1 Yes | 2 No |
How do we measure quality of testing? What are parameter of this?
How can u do the performance testing?
how to know whether the bug is valid or invalid?
if bug is found & we will know the main Resion for that bug Arrise 1 - Corrective & Prevention Action 2 - Risk ana 3 - Root Cause analysis 4 - Impact analysis
what is performance testing
what is traceability matricks
How we prepare the Requirement Traceability Matrix(RTM). Write the format please.
What is inter-operability?
what is production defects?
Do testers have to write separate test cases for performing sanity testing??
What are the different ways of writing test cases?
"Why are you looking for a change?". This is the common question that is asked in any interview. Can anyone tell me wat kind of answer would impress the interviewer.
Automation Testing 
