Answer / satya

Hi,

- If the bug rate falls certain level.
- if the build is not stable.( if the main
unctionalities are not working )
- if there are lot of change requests(CR's).
- And all the functional requirements are covered.

Let me know if there any mistakes.



Regards,
Satya.k

Answer / sangamesh

In many condition we hav to stop Testing:

1) If Specification is not proper
2) If so many so many show stoper bugs are their
3) Functionality is not meating to the Specification
4) Environment is not proper to test (System Environment)
.....

Answer / tztexas

When you meet your Exit Criteria that was in the Test Plan
you wrote before testing began. AND this test plan would
have been approved by key stake holders.

If you cannot meet your Exit Criteria, it is the Key stake
holders who make the decision to stop testing. When this
happens they should be aware that they are now responsible
for the quality of the system that was not tested.

Answer / prakash.j

all the above answer is right but the question is open
ended it is tricky one - boz we can keep on do the testing
if you are going to upgrade the requirement - always every
concern want to upgade with latest tech. - until it full
fill the custmer requirement and needs the quality within
the time frame and cost then we can stop testing

Answer / allwin

Typically testing is an endless process.

- When the project meets its dead line.
- After client finishes his UAT testing.
- When we execute all the test cases.
- After all the functionality works.
- When test budget is reached

V.Allwin
helloallwin@gmail.com

Answer / parmar.ic@gmail,com

1.When there is no time and budget
2. When maximum number of test cases are executed
3. All the Requirements are mapped that is RTM is filled
completely
4. When Test coverage is > 80%
5. when bug rate falls below certain level
.

Answer / jethva_trupti

It depends on the level of risk, including technical,
safety, and business risks, and project constraints such as
time and budget.
When there is no time and budget
when you meet exit criteria
when your certain amount of test cases executed

Answer / sujatha

Hai,

According to my knowledge we can't say when we r going to
stop the testing.But.........
1.As soon as the code meet the previous agreed up on the
defects per KLOC
Ex: take the project, that project can be released when
there is an average errorpercentage of .2 defects per KLOC
2.when the cost invested on testing exceeds the revenue
that can de incurred by the testing

Answer / shobha

1.When the allocated time exceeds, allocated cost exceeds
2.When deadlines are met
3.showstoper kind of issue is found
4.bug rates fall below certain level
5. when test cases are complete

Answer / meenakshi

1. When there is no time and budget
2. When maximum number of test cases are executed
3. All the Requirements are mapped that is RTM is filled
completely
4. When Test coverage is > 80%
5. when bug rate falls below certain level

What is difference between JBOD and RAID?

0 Answers   IBM,

wat r d schedules for testing?

0 Answers   Mind Q Systems, QA Planet,

What is validation and verification testing?

0 Answers  

Explain virtual memory?

0 Answers  

Other than Mr Nageshwar rao anyone suggest me the other best institute to go for testing.

5 Answers  

What are the different Metrics followed in the project?

1 Answers   Cap Gemini,

What is future of FC SAN vs FCOE SAN

0 Answers  

Which tool you use to debug SQL Queries

2 Answers   SumTotal,

Given alone a functional specification docs if a test plan is to be prepared without any prototype and the product or the appli is to be delivered within 10 days ..How to prepare test plan and prepare test cases ? Cheers, Amar.gp

2 Answers   Wipro,

What is boundary value?

0 Answers  

Explain compatibility testing?

0 Answers  

tell some examples for driver and stub?

0 Answers