Software Testing - when we know that testing is complete?

GeekInterview.com > Interview Questions > Testing > Software Testing

Go To First | Previous Question | Next Question

Software Testing | Question 35 of 256

when we know that testing is complete?

Total Answers and Comments: 4

Last Update: July 12, 2008 Asked by: prakash_534

Sponsored Links

Best Rated Answer

—

No best answer available. Please pick the good answer available or submit your answer.

February 09, 2006 04:17:59

Abhay Kumar Tripathi

RE: when we know that testing is complete?

There are some points which indicate that testing is complete:

1-The exit criteria that was mentioned in the test plan document is achieved.

2-when we acheived no. of successful test case execution at a specified level.

2-when rate of bug finding decrease from a specified level.

3-when manager said that ok stop.

4-when we dont have enough time to perform more test and have acheived a specified level of quality.

5-when the cost of fixing a bug ismore then the impact of the bug in the system.

Is this answer useful? Yes | No

September 22, 2006 03:29:55

venkatesh

RE: when we know that testing is complete?

That is complicated question. As far as build remains testing remains.

when ever customer requests for new featuere at that time complete and pure regression testing takes place.

thank u

regards

venkatesh

Is this answer useful? Yes | No

December 10, 2006 02:02:01

sudhakar2068

Member Since: July 2006 Contribution: 390

RE: when we know that testing is complete?

we know that testing is complete when all bug status in the life cycle are closed.

Sudhakar

My Email:kollasudhakar2005@yahoo.co.in

Is this answer useful? Yes | No

0 1

Overall Rating: -1

July 12, 2008 03:38:06

StevenPace

Member Since: July 2008 Contribution: 30

RE: when we know that testing is complete?

God will decend and gently stroke your cheek, telling you that you did well my son. Seriously, how could it ever be complete? The question is one of balancing compeating priorities. Sometimes marketing pressures require a product to be released early DOS 6.0 is a classic example, it just "wasn't ready" in the words of one team member I talked to. The way that you know it is ready is that the bug counts are low, especially the critical bugs.

Is this answer useful? Yes | No

Go To Top