When to Stop Testing?
Answers were Sorted based on User's Feedback
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
| Is This Answer Correct ? | 7 Yes | 0 No |
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)
.....
| Is This Answer Correct ? | 5 Yes | 1 No |
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.
| Is This Answer Correct ? | 3 Yes | 0 No |
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
| Is This Answer Correct ? | 0 Yes | 0 No |
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
| Is This Answer Correct ? | 1 Yes | 1 No |
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
.
| Is This Answer Correct ? | 0 Yes | 1 No |
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
| Is This Answer Correct ? | 0 Yes | 1 No |
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
| Is This Answer Correct ? | 0 Yes | 2 No |
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
| Is This Answer Correct ? | 0 Yes | 3 No |
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
| Is This Answer Correct ? | 0 Yes | 3 No |
Hi, I attended an interview recently. I was asked the following question Assuming that I am Test Manager. There are 20 resources out of which 12 are manual testers, 5 automation testers and 3 performance testers. There are a bunch of projects to be tested in the organisation, the projects belong to various technologies, say 20% of projects in Java, 20% of projects in SAP, 30% of projects in .NET, 30% of projects in C# What is your approach as Test Manager in testing? Pls let me know your approach on this.
I need to learn everything I can about the SDLC. What is the best online resource?
Every One is saying that Documentation is very very importent in Tester's Life.Could any one explain with proper examples..?
I wanted a good defect tracking system and had selected one when one of my friends suggested Zephyr 2.0 being a good test management system that too with an integrated defect tracking tool. Would like to know from those who have used it whether Zephyr is a good investment?
What can static analysis not find?
Following questions were asked in amazon interview during written test for the post of Quality assurance engineer. Note. u can use any scripting language for 2nd 3 rd questions. Logic is important. 1.Write test cases for file transfer using bluetooth and IR in mobile⦠2. Input = 193 the output should be displayed as 100+90+3. Write code without using inbuilt functions and procedures 3. string = performance and delimiter = r Write a code to display the output as Pe r For Man Ce Without using split function and inbuilt functions 4. please give correct test data for the remainder in the below program and also for the time TIME: DD MM YYYY HH MM SS Reminder: [ ] minutes
Why is the decision table testing used?
What the different types of test coverage techniques are?
What is Unit Testing?
What is control structure testing?
What is variable trace?
What is assertion testing?