Answer / balakumaran.l.s

a.New:
When a bug is found/revealed for the first time,
the software tester communicates it to his/her team leader
(Test Leader) in order to confirm if that is a valid bug.
After getting confirmation from the Test Lead, the software
tester logs the bug and the status of ‘New’ is assigned to
the bug.
b.Assigned:
After the bug is reported as ‘New’, it comes to the
Development Team. The development team verifies if the bug
is valid. If the bug is valid, development leader assigns
it to a developer to fix it and a status of ‘Assigned’ is
assigned to it.
c.Open:
Once the developer starts working on the bug,
he/she changes the status of the bug to ‘Open’ to indicate
that he/she is working on it to find a solution.
d.Fixed:
Once the developer makes necessary changes in the
code and verifies the code, he/she marks the bug as ‘Fixed’
and passes it over to the Development Lead in order to pass
it to the Testing team.
e.Pending Retest:
After the bug is fixed, it is passed back to the
testing team to get retested and the status of ‘Pending
Retest’ is assigned to it.
f.Retest:
The testing team leader changes the status of the
bug, which is previously marked with ‘Pending Retest’
to ‘Retest’ and assigns it to a tester for retesting.
g.Closed:
After the bug is assigned a status of ‘Retest’, it
is again tested. If the problem is solved, the tester
closes it and marks it with ‘Closed’ status.
h.Reopen:
If after retesting the software for the bug opened,
if the system behaves in the same way or same bug arises
once again, then the tester reopens the bug and again sends
it back to the developer marking its status as ‘Reopen’.
i.Pending Rejected:
If the developers think that a particular behavior
of the system, which the tester reports as a bug has to be
same and the bug is invalid, in that case, the bug is
rejected and marked as ‘Pending Reject’.
j. Rejected:
If the Testing Leader finds that the system is
working according to the specifications or the bug is
invalid as per the explanation from the development, he/she
rejects the bug and marks its status as ‘Rejected’.
k.Postponed:
Sometimes, testing of a particular bug has to be
postponed for an indefinite period. This situation may
occur because of many reasons, such as unavailability of
Test data, unavailability of particular functionality etc.
That time, the bug is marked with ‘Postponed’ status.


l.Deferred:
In some cases a particular bug stands no importance
and is needed to be/can be avoided, that time it is marked
with ‘Deferred’ status.

Balakumaran.L.S
CAC software
Chennai.

Answer / jmk

Open
Assign
Fix
Retest
close

Answer / vidya

1)New
2)Open
3)Assign
4)Reopen/Rejected/Deferred
5)Closed

Answer / sudhakar reddy

There diffrent stages in the bug life cycle they r as
follows
1)NEW
2)OPEN
i)DUPLICATE
ii)REJECTED
iii)POSTPONED
3)ASSIGNED
4)FIXED
5)VALIDATE(after vlidationif the bug is still not not fixed
it is rejected n sent back to (OPEN))
6)CLOSE

Answer / naik

In the process of test case execution, if at all any defect
is detected, its raised in the defect tracking tool with
status "NEW".

Now the defect is assigned to the concerned developer by
the Lead. Now the status is "OPEN".

If the developer rejects that defect, the status will
be "REJECT".

If the developer accepts the defect, after fixing the bug,
he changed the ststus to "FIXED".

Now tester re-tests that particular fix. If the bug is
fixed, then the status will be "CLOSED". Otherwise he again
raises the issue changing the status to "RE-OPEN".

Answer / ramprasad.s

Hi

Anuja

Bug Life cycle

1. Open
2. Review
3. Assign
4. Fixed
5. Retest
6. Closed
7. Deferred.

sun_ramprasad@yahoo.com

Answer / shalini

Hi Balakumaran. Excellent ans posted from you.Vey good.Keep
it up.Keep posting.It will be very useful

Answer / anuja

Thanx rajesh, jmk & vidya for answering me but I Wan
detail.. explaination so p/z send me details..Thanx once
again..

Answer / akku

new
open
rejected
closed
reopen
assigned
retest

Answer / satya priya

new
open
assign
test
verified
deffred
reopened
duplicate
rejected
closed

Plz any one explain with example for a high priority with low severity and low priority with high severity bug

1 Answers  

In usability testing we check spelling, content, look and feel, color combination, link or menu navigation? please let me know more about usability testing.

0 Answers  

What is acid testing

4 Answers  

Name some bug tracking tools???

3 Answers  

how to report a bug to the developer?What is the structure of Bug tracking?

4 Answers  

when we swipe the credit card what will genertaed in Back end. how system will validated from the back end for credit card who is Aquriree and Issuer ,

1 Answers   MetLife, Quark,

If there is only one module or unit then how you test it?

1 Answers  

Explian about boundary value analysis with an example ?

4 Answers   RTG,

suppose 10 mangoes cost is 300 rs with 10% discount in this case u r writing 10 test cases.u want to change that cost to 500 rs in this case u r writing 5 testcases....... so, how many functional test cases and how many regression testcases in these 15 testcases?

0 Answers  

What is severity ?

4 Answers   CSS,

Hi Frds., i am Nithi here.here in my company i am working in manual testing ie. application testing only front end not back end like i will enter datas and check whether the record gets updated r not. what kind of testig is this? and some people r working on scripting languages same manual testing what is the difference between these two testing? ans please thanks in advance

3 Answers  

Test cases for Recycle Bin

4 Answers   Quexst, Shriram,