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 All, I am new this site also new to testing Domain, I am BSc (CS) Student 2010 passed out. I am planning to do Testing Course, some of them suggesting QAI Certificate Course. Could any one suggest is these certificate will useful to get the Job ? or QAI sitable for whom ? Thanks Saran
plz give me any body some 3top UAT test cases, Advance thanks?
I am asking this question out of my interest. Geneva Billing tool is used by BT to generate bills, what is the process to execute the test cases manually..do i need to write SQL query or it is a GUI based tool. Thanks..
This question is based on ages easy.
How u r breaking down the project among team members?
what is the difference between the normal testing and embedded testing?
What are the types of defects?
What parameters to consider for Performance Testing?
what is the difference between defect management tool and tesecase managment tool, what are its purpose, does QC and TD use for both(defect &test case managment)
what is the diff between test strategy & test methodology?
Explain glass box testing?
What are the main bugs which were identified by you and in that how many are considered as real bugs?