explain bug cycle

Answers were Sorted based on User's Feedback



explain bug cycle ..

Answer / kkira

Hi
Once the tester finds the issues the tester give the
status of the issues is NEW
Then the tester assigned to developers then status of
issues is Assigned
Then the developers open issues then the status of issues
is OPEN
After the issues is fixed and gives the modify build
Then tester testing the issues is fixed are not? If fixed
the status of issues is FIXED
If you not fixed the status of issues is REOPEN
Some times based on priority and severity the developers
give and (tester ) status will be changes like deferred

Is This Answer Correct ?    6 Yes 0 No

explain bug cycle ..

Answer / nancy

NEW--> when the tester find the error or mistakes in the
application
ASSIGNED-->It will be assigned to the developer who
developed the application
FIXED--> The status of the bug will as fixed after it fixed
by the developer
VERIFY--> It should be verified by the tester once it fixed
and it will be REOPENED only if the bug remains the same or
else
CLOSED--> It will be closed

Is This Answer Correct ?    6 Yes 0 No

explain bug cycle ..

Answer / sandeep

Identifying and Reporting the bug--assign the bug--evolution
of the bug--Fixing the bug0--Verifying the bug----Closing
the bug

this is the bug life cycle.

Is This Answer Correct ?    3 Yes 0 No

explain bug cycle ..

Answer / sakthi

open

PM analyses

assigned or defer

developer fixes

fixed

tester checks

checked - if not satisfied, the tester reopens.

tester closes

closed

Is This Answer Correct ?    3 Yes 1 No

explain bug cycle ..

Answer / pavithra

Hi all,

Bug Life cycle contains many phases

New-When a test engineer raises an issue.

Assigned-Issue will be assigned to the developer.

Fixed-The bug is fixed by the developer.

The bug is retested.If it works fine then Closed will the
bug life cycle phase.

Is This Answer Correct ?    2 Yes 0 No

explain bug cycle ..

Answer / aarinari

EXPLAIN BUGLIFECYCLE:



BUG LIFE CYCLE is the movement of the bug in different stages.
after understanding the functional requirement specifications
the developer will develope the module after that it will go
to the testing team.
as a result of testing if any defects are found. then it
will be OPEN/NEW bug.
if there are no any defects testing will be stopped. again
these open/new bugs
will be send to the developement team for fixation.then the
developer will see whether
it is really a defect. if it is really a defect then it will
be rectified.if it is not
a defect then again there will be 3 stages like HOLD, AS PER
DESIGN, TESTERS ERROR.
the rectified defect will be again sent to the testing
team. then due to the result
of the regression testing if the defects are rectified then
it will be CLOSED.
if the defects are not rectified then again it will be
RE-OPEN. this is BUG LIFE CYCLE.

*************

Is This Answer Correct ?    2 Yes 0 No

explain bug cycle ..

Answer / savita

Defect life cycle:first step is to see whether defect is
opened or new.if it is so then first is to see which all
defect is to be rejected ,fixed in new release,not
reproduced etc.and there may be some defects which are small
at the core of application that defects cant be fixed..some
are not reproducible for example were environment is
mismatch or build is mismatch in such case it is not
reproducible.
so 1)OPEN/NEW
2)ASSIGNED
3) FIXED
4) RETESTED
5)OPEN /CLOSE..
thank u...............

Is This Answer Correct ?    2 Yes 0 No

explain bug cycle ..

Answer / sathya

BLC
New this is new status of new applications. Done by a TE.
Open if any defect found this status set to open condition,
send to developer done by a TL
Fix after rectify the defect if status change to fix, send
to tester. Done by a Developer.
Reopen if any defect found again this status change to
reopen condition done by a TE/TL.
Close all defects rectify this status change to close stage.
Done by a TE/ TL.

Is This Answer Correct ?    2 Yes 0 No

explain bug cycle ..

Answer / karthick407

Bug: Deviation from the client requiremnet.
Bug life cycle:

1.New : When executing the test cases, if the tester
found any defects, he would rise a bug with the status NEW.
2.Once the bug is raised , it will be send to the
developer who works on the module with the status ASSIGNED.
3.Once the developer fixed the bug. It would move to
FIXED status.
4.Tester will re execute the test cases which are failed
initially. If The test case is pass then the he will CLOSE
the bug.
5. if still the bug araise, again he would send it to
the developer with the status REOPEN.

this cycle will go till all the bugs are fixed and all
test cases are pass.

Is This Answer Correct ?    1 Yes 0 No

explain bug cycle ..

Answer / suman

HI SAKTHI UR ANSWER IS CORRECT.

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Manual Testing Interview Questions

What is the testing process and what testing process followed by software company?

2 Answers  


what is test metrics? difference between test matrix and test metrics? (Asked in Zensar Hyderabad today(17-1-12010))

1 Answers   Zensar,


who prepares the use cases?

4 Answers  


how you r executing Test case explain in detail

2 Answers  


what is framework and what is test methodology? (Asked in Zensar Hyderabad today(17-1-12010))

1 Answers   Zensar,






Whether the testing process followed in different model will be same or will it vary?

1 Answers  


What is the sdlc? what is the mannual tester roles? Write test case............? Sqlquerries...? How many test cases do you write down  perday.........?

2 Answers  


Which things do you examine in requrement while writing testcases.

1 Answers   Datamatics,


how can u do database testing manually?

4 Answers   HCL,


how many types of functions in qtp

1 Answers  


can u write test cases for telephone?

9 Answers   Professional Access,


what are all the things we will include in " what to be tested and what not to be tested" in Test Plan

0 Answers  


Categories