Interested to Buy Any Domain ? << Click Here >> for more details...
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 Catapult Testing in E-Learning Domain?
how mapp the defect id in quality center?
What is revision history and the content of revision history table?
What are the differences between stlc and sdlc?
Can any one give a summary of testing a territory management system? what would be the test scenarios, few test cases. how it works.
what is the difference between test case and result matrix
which test strategy your are fallowing in your company?which documents u r using in software development life cycle?
Do you think tools are required for managing change. Explain and please list some tools/practices which can help you managing change.
You want a automation tool to be used for your project. How will you convince the client for the same. Please give me specific answer.
Can you explain boundary value analysis?
What were the major challenges u faced while testing
Information about Automated Software Installer
Can you explain the elementary process?
what is the difference between section & test feature in test case documention?
Does an increase in testing always improve the project?
