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

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

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.

Answer / sakthi

open

PM analyses

assigned or defer

developer fixes

fixed

tester checks

checked - if not satisfied, the tester reopens.

tester closes

closed

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.

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.

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

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...............

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.

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.

Answer / suman

HI SAKTHI UR ANSWER IS CORRECT.

define with example high severity and low priority ? 2.low severity and high priority? 3.both are high? 4.both are low ?

2 Answers   ACS, Siemens, TCS,

black box techniques

4 Answers  

!. what are the entry eriteria for functiondity and performance testing ?

1 Answers  

what r the requirments & inerview questions for the test lead in testing?

1 Answers  

Who writes "white box " test cases ?

4 Answers  

wat is Bottle Neck testing

4 Answers   Saksoft,

What is bug priority?

0 Answers  

When we perform re-testing?

6 Answers   eZest,

How can you do the usability testing?

0 Answers  

can any one define V-V testing?....thanks in advance

3 Answers  

How many days need to test one module?If any one know the answer please tell me?

2 Answers  

What is the maximum length of the test case we can write?

4 Answers   Sonata,