hi Friends this is Srinivas. Can u discribe about bug
lifecycle.how to say in interview.send me my mail
:dsrao106@gmail.com

Answers were Sorted based on User's Feedback



hi Friends this is Srinivas. Can u discribe about bug lifecycle.how to say in interview.send me my..

Answer / sm

Bug Life Cycle:

1)Bug life cycle starts with "New" status
2)Then the test Engineer reports this bug to Developer with
status New
3)If the reported bug is accepted by the developer he will
change the status to "Open"
4)Then after fixing the Open status bug he will sends it
back to the tester with a status "Fixed"
5)After the test engineer again tests the same reported bug
and he/she makes it as closed if the bug is "Closed"
completely or else they will sends it back to the developer
with a "Reopen" status.
6)The precess will go like this till the bug status comes to
closed.

New
/ | \
/ | \
/ | \
Deferred Open Reject
| |
| |
Fixed Closed
|
/ \
Closed Reopen

Is This Answer Correct ?    1 Yes 0 No

hi Friends this is Srinivas. Can u discribe about bug lifecycle.how to say in interview.send me my..

Answer / prasanna babu.v

New/ open: – Whenever the test engineer identifies the
defect newly for the first time then he will set the states as
new/open. But some companies will say it as new and once the
developer accept as defect he will set as open.
Fixed for verification: – Whenever the test engineer raises
the defects and the developer rectifies it the he will set
the status as of the defect as ‘Fixed for verification’
before releasing the next build.
Reopen and Closed: – Whenever the defects are rectified and
next build is releasing to the testing department then
the test engineer will check whether the defects rectified
properly or not if they feel the defects is not rectified
properly then they will wet the status as ‘Reopen’ if at all
they feel that the defect is rectified properly then they will
set status as ‘Close’.
Hold: – Whenever the developer is in a confusion situation
to accept or reject the defect in such situation he will set
the status as ‘Hold’.
As per Design: – Whenever the new requirements are given by
the development team and the developers
incorporated those new fields and release to the testing
department. As the test engineers are not aware of those new
changes he will raise as them defects. But the developers
will set the status as ‘As per Design’.
Testers Error: – If at all the developer feels it is not at
all a defect then he will set the status as ‘Tester Error’.

Is This Answer Correct ?    0 Yes 0 No

hi Friends this is Srinivas. Can u discribe about bug lifecycle.how to say in interview.send me my..

Answer / ravi kiran

New
|
Open ___ Deferred
| |
___Assign ---|
| | | ___ Rejected
Reopen |
|___Test
|
Verify
|
Close

First once the bug is found it is said to be in new state,
i.e. it is not at confirmed (approved). After it is
confirmed it is assigned and then in Testing. After
verified and if fixed then the bug is Closed.
Else it is reopened and then again assigned.
After assigining some times it is deffered to other
releases or some times rejectd.

Is This Answer Correct ?    0 Yes 0 No

hi Friends this is Srinivas. Can u discribe about bug lifecycle.how to say in interview.send me my..

Answer / pradeep kumar

First the BUG will be in "New" stage, it will go
into "Open" stage, now it will go into "analys" stage there
it will be analysed by project manager/product manager with
the presence of development lead, if it is not a correvt
bug they can "Reject" the bug and if the bug is corrected
for next release then it can be send to "Defer" stage, and
if it is a perfect bug it will assigned to particular
developer in "Assign to fix" stage. Then "Retest" it
in "Retest" stage., here if bug is not fix correctly it
will be send to "Reopen" stage, if bug is fixed correctly
then it will be send to "Close" stage

Is This Answer Correct ?    0 Yes 0 No

hi Friends this is Srinivas. Can u discribe about bug lifecycle.how to say in interview.send me my..

Answer / soumya prasad

1)Bug life cycle starts with "New" status
2)Then the test Engineer reports this bug to Developer with
status New
3)If the reported bug is accepted by the developer he will
change the status to "Open"
4)Then after fixing the Open status bug he will sends it
back to the tester with a status "Fixed"
5)After the test engineer again tests the same reported bug
and he/she makes it as closed if the bug is "Closed"
completely or else they will sends it back to the developer
with a "Reopen" status.
6)The precess will go like this till the bug status comes to
closed.

New
/ | \
/ | \
/ | \
Deferred Open Reject
| |
| |
Fixed Closed
|
/ \
Closed Reopen

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Automation Testing AllOther Interview Questions

I am testing a GIS based application so Can anyone tell me which automation testing tool is best for this application?

0 Answers  


default time for executing 1000 lines of script in winrunner and also in qtp.

3 Answers   Accenture,


plz explain QTP real time work( Means where you store scripts and how u access scripts next day? where those activities we are maintaining, If By usig VSS how the process in going on , plz explain briefly?

0 Answers   CTS,


Tell us the difference between assert and verify commands?

0 Answers  


Difference between winnrunner and qtp?

2 Answers   Ordain Solutions,






What tools are available for support of testing during software development life cycle?

2 Answers  


What are the main attributes of test automation?

0 Answers  


What are the risks associated in automation testing?

0 Answers  


What are the disadvantages of Hybrid framework

0 Answers  


Hi All, I am looking selenium training in Hyderabad. can any one tell me the best training institute/trainer?

6 Answers   QE, QEdge,


What is testng and why is it better than junit?

0 Answers  


What is junit? And what is junit annotation?

0 Answers  


Categories