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 clarify functional requirements and non functional requirements in a srs?

2115

---

What are the two main categories of software testing?

1218

---

How to test the search functionality.For example in naukri advance search is there.how ca i test that page.

2175

---

1)What are the QA procedures followed 2) Write test cases on a weatherreport.com web page that has only two dropdown and a submit button, Fist drop down is a countries and second is metros in the selcted countries.When proper selection si doen and submitted it shows weather report of that metro.? 3)Write test cases on Mobile Alarm Module? 4)Write test cases on Company Water Bottle?

3142

---

What are the disadvantages of manual testing?

1255

---

What is black box testing, and what are the various techniques?

1205

---

What is an inspection in software testing?

1230

---

what are the tests u did in entire project? when it did in the project? (means at the release build to end of project) plz explain clearly

2142

---

what is diffrence between dynamic black box testing and dynamic white box testing

2018

---

what is the testing approach for windows Explorer(Not IE Explorer)

2794

---

How to do the performance testing manually? Does you have a test case for that?

1175

---

what is test case management?explain in brief.

2089

---

How will u decide test data to see that evey feature is thoroughly tested

2078

---

What is a failure?

1260

---

What is manual testing and what is it process?

1626

---