Answer Posted / anupama

Statuses associated with a bug:
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.

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.

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.

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.

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.

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.

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.

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

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

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

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.

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

how to indentify memory leakages after the build

2083

---

write test case for gmail login page

5166

---

Describe a past experience with implementing a test harness in the development of software.

3902

---

is it possible to do performance testing in stand alone application..how wil u do that ???????

2222

---

What are the main key components in Web applications and Client Server applications? and their differences?

2019

---

Q) Create Preffered customer: As a customer when i purchase more than $5000 in goods since my first purchase, I become a preffered customer so that i can receive the benefits associated with that status.

2520

---

Explain the strategy for testing a Java application?

2094

---

What exactly you do as a Configuration controller?

1956

---

What are the different servers and difference between them?

2119

---

Do you use any automation tool for smoke testing?

1218

---

How we test the bulk of contents in web page using manual testing? Is any open source tool available for that ? Thanks in advance..

2004

---

1.what is the approach while writing test cases in your project. 2.tell some intresting scenareo in your project

2231

---

What does 100% statement coverage mean?

2206

---

If there is non reproducible bug which developer is not ready to agree, how you will convince him.

8867

---

Explain Single View Testing ?

1372

---