mchauhan

 Profile Answers by mchauhan 

• Oct 25th, 2005

 

It decided by Test Manager/Leader based on his schedule and delivery for the product to be tested and percentage of testing to be done on the product, rather testing is a endless process which cann't last until 100% testing is done by all respect.

-Mukesh Chauhan Banaglore 

mchauhan

 Profile Answers by mchauhan 

• Oct 25th, 2005

 

Test Manager/Leader decides on the basis of their schedule and delivery for the product to be tested and percentage of testing to be done on the product, rather testing is a endless process which cann't last until 100% testing is done by all respect. Mukesh Chauhan -Banaglore

supriya

• Nov 16th, 2005

 

Testing is a never ending process.Testing can be stopped when maximum number of test cases are executed and have been passed,when deadlines are reached,when testing budget depletes,when basic functionalities are working

Dan

• Dec 3rd, 2005

 

This is usually not a difficult decision. When all critical, serious and blocking issues have been fixed we have to test until the product is shipped and even after. The testing cycle is an endless process. Only the type of testing might vary from one stage to another in the development cycle of the product.

Choudary

• Dec 7th, 2005

 

As of my knowledge following parameters should be consider to decide a S/W tested enough

1) Bug Rate

2) Schedule

3) Budget

4) Test Case Covarage

5) Risk Analysis ( Means all risk areas covered or not)

Any one criteria of above will not serve the purpose.Based on company priorities we have to take optimal decision by considers all above parameters

Ravi Kochar

• Dec 30th, 2005

 

we can decide same on following bases.

1) We define Pass Criteria in Test Plan and if Pass Criteria matches with our scedule or current scenario we are in situation to say that we have tested enogh.

2) I t can be decided by , how many priorities items are left to test, how many are already tested, and how much time will be taken for doing the same,

we match all these with our Pass Criteria then discuss withour concerned manager and can take decisson that we have tested enough.

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Dec 20th, 2006

 

Hi,

It is decided by Test Lead. Here are some points to decide when to stop testing
Deadlines (release deadlines, testing deadlines, etc.)
Test cases completed with certain percentage passed
Test budget depleted
Coverage of code/functionality/requirements reaches a specified point
Bug rate falls below a certain level
Beta or alpha testing period ends

Regards
Prasad

jay

• May 13th, 2007

 

I like the other answers above.  However, my answer would be when the criterias for the product or software being tested have all been met.

M.Vimal Danish

• Jun 6th, 2007

 

Its never ending process. Still the testing process can be stopped

(1) Based on the Testing dead line and Release dead lines

(2) Based on the number of test cases covered with certain percentage passed

(3) Based on the coverage of code,functionality,module,requirement reaches to the specified level

(4) When the bug rate falls to down

(5) When alpha or beta testing period ends...

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 17th, 2009

 

You have tested enough when the company's Exit Criteria have been met.  This typically includes (not an exhaustive list):

1) All test cases have been run or are otherwise accounted for
2) There are no blocked or partially completed test cases.
3) All test cases have passed unless they are reported as defects
4) There are no 'Open' defects
5) All showstopping defects must be 'Closed'
6) The number of 'Unresolved' defects by Severity and Priority meet the thresholds which were agreed upon by all relevant stakeholders in the client and provider organizations