Answer Posted / 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.
| Is This Answer Correct ? | 4 Yes | 0 No |
Post New Answer View All Answers
What is a critical bug?
What is junit & api?
how to test a store procedure?
What is the first test in software testing process?
how to access a build & wat is its configuration
3. In a system designed to work out the tax to be paid: An employee has £4000 of salary tax free. The next £1500 is taxed at 10%. The next £28000 after that is taxed at 22%. Any further amount is taxed at 40%. To the nearest whole pound, which of these groups of numbers fall into three DIFFERENT equivalence classes?
What is XML Testing? Do we have any tools to test the XML? Please let me know.
1.Tell me negative test cases for notepad 2.Tell me the factors for for writing severity based test cases
What is an exit criteria?
Can any one share the domain knwoldege of Telecom Jeeva jeevachr@gmail.com
How can data caching have a negative effect on load testing results?
What is AGP?what is setup.inf?What are the ways to install driver?
Which criteria should take in account while doing CMS testing of any project?
what is sanity test (or) build test?
How can software qa processes be implemented without stifling productivity?
