Explain Bug Life Cycle and expalin briefly each 'Status'
also
- 4 Answers
- 7933 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / sailaja
BUG Life cycle starts at the developer.due to developer
fault or overlook or mis understanding, bug will be
included into the software-> tester will find the bug
during testing and set the status to 'new bug found'-> goes
to the test lead he will review on that and set the status
of the bug and allocates to the developer-> developer fixes
the bug or if it is not a bug then clears the testing
department and sets the status-> test lead will give the
report to the tester -. tester tests the applilcation for
the bug and updates the status-> if the tester has the
previllage to change the status to "Fixed" he will change
or else he will give the report to the test lead then he
will set the bug status to "Fixed"
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / manoj
the process that we have sharing with you...
a bug cycle start from tester end, he/she log that defect
in tool as Open that goes to developer.
Developer look into that and mark fixed by making the
change in code w.r.t to bug. and send that bug to tester
with a new build, tester re-test that again if its actually
fixed tester close the bug other wise re-open and send
again to developer
| Is This Answer Correct ? | 1 Yes | 0 No |
When a Tester find a defect in an application, he will send
the defect report to PL with status as NEW. He will check
the defect whether it was bug or not. If it was bug, he
will change the defect status as OPEN and send it to the
corresponding developer to fix it. The Developer fixes the
defect and change the status as FIXED and send it to the
Test Engineer. The Test Engineer performs Retest and
Regression Testing on the modified build. If the bug was
fixed he will change the status as FIX-VERIFIED. other wise
he will change the status as RE-OPEN. If the bug was fixed,
he will send the defect report to the Test Lead with status
as FIX-VERIFIED. The Test Lead will CLOSE the defect.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / phani
an error made by developer during coding is called as error.
when error detected by test eng when testing is called as
defect.
when defect accepted by devolper and ready to fix is called
bug.
defect identification(new or open)
==>reprodusable or not(verified by testor itself)
==>reporting to dev team(via tL)
==>accepted converts to bug
==> bug fixing or resolving
==>regression testing&re testing
==>bug closing.
by
phani
| Is This Answer Correct ? | 0 Yes | 0 No |
Hello, Is there any source from which i can get any live tutorial or trial of Automation tools?? Also i have a query that is there any certification course or exam available for Automation tools QTP and QC?
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?
What automating testing tools are you familiar with?
What is the purpose of the testing?
Does automation testing have any disadvantages?
What are the most popular tools for automation testing?
How to find that tools work well with your existing system?
Hi all, Do anyone have the experience in PDF Document Automation using OLE objects and methods? If so suggest the best websites for source. Thanks :-)
If a scenario is given and asked whether we can automate the system according to that scenario,how wil we answer such type of questions?
hi every one this is ashok pls any one give answer me pls question is while testing with selenium after giving id user name and password , the inbox will be open , how to handle this one
Tell us what automation tools could be used for post-release validation with continuous integration?
Write a short compiled module which selects random numbers?
WinRunner 
