When to start and Stop Testing?
Answers were Sorted based on User's Feedback
Answer / sj1234
This is a General question asked in all the Interviews
You start testing once you are clear with the requirements
amd the documnets are ready
You stop testing depending on the following factors
| Is This Answer Correct ? | 26 Yes | 6 No |
Answer / sudhakar8
The following are the list of items that are required to be
Start the QA Phase.
.Complete Unit/ Integration Testing.
.QA Test Environment SetUp Completed.
.QA Test Plan Preparation Completed and approved.
.QA Test Cases Preparation Completed and approved.
The following are the list of items that are required to be
Stop the QA Phase.
. All Planned System Test cases have been executed.
. No Critical Bugs.
. Defect log should be updated.
. QA Test Summary Report Completed.
. QA Sign off.
| Is This Answer Correct ? | 10 Yes | 1 No |
Answer / sj1234
I am continuing The answer You stop testing when
stop testing these are the main factors.
1. Reduce in defects.
2. Increase in Testing cost.
3. Delivary dates.
We need to check that
1) Whether all the Bugs which were Assigned to developers
have been fixed .
2) All the documents pertaining to testing have been
prepared.
3) all the bugs which were in Previous releases have been
retested .
| Is This Answer Correct ? | 16 Yes | 8 No |
Answer / divya nandana.b
we will start testing when we have software requirement
specification, enough testcases, and build
we will stop testing
i)when all major seviority bugs are solved
ii)when budget is going to complete
iii)when project time s going to complete
| Is This Answer Correct ? | 6 Yes | 3 No |
Answer / meenakshi
when bug rate falls below a certian level
when deadlines are reached
when all the testcases are passed with a certian rate of
passed testcases
when testing budget is depleted
and teamleader says to stop testing
in all these cases we stop testing
| Is This Answer Correct ? | 5 Yes | 6 No |
Some of the common factors and constraints that should be considered when decided on when to stop testing are:
1. Testing budget of the project. Or when the cost of continued testing does not justify the project cost.
2. Resouces available and their skills.
3. Project deadline and test completion deadline.
4. Critical or Key Test cases successfully completed. Certain test cases even if they fail may not be show stoppers.
5. Functional coverage, code coverage, meeting the client requirements to certain point.
6. Defect rates fall below certain specified level & High priority bugs are resolved.
7. Project progresses from Alpha, to beta and so on.
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / nandini pai
Enter criteria to start testing:-
Build is released to testing team with all unit test case is executed and all defect got fixed which is identified during unit testing
Stop Testing(Exit criteria ):-All Business requirement is testing and all defect are fixed
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / prabha
When to start:
1)When build is ready
2)Environment is setup
3)Test cases are executed
4)Resource should be ready
when to stop:
1)Based on no. of test cases executed
2)No. of defect-reach certain low level
3)Based on release date
| Is This Answer Correct ? | 3 Yes | 5 No |
Answer / prince
why no hv mentioned abt the Test Plan -Exit Criteria.
while Test Plan is done we use to mention the Exit Criteria
Right,we shd Indentify that Exit Criteria also to Stop
Testing know?
| Is This Answer Correct ? | 1 Yes | 4 No |
What is the involvement of tester in SDLC?Explain.
What are the challenges you faced related to production environment bug?
If a company does not contain any maturity levels?Do u think the company does not have quality?Discuss?
SDLC Phase ==> Requirements feasibility study --> understanding of design / architecture --> development of DFD/Use Case diagrams / Stories etc --> development --> v&V --> Acceptance. Request you all to identify all possible artifacts created during SDLC phases.
what is test condition
wat will be your testing approach for this product from project start to finish(product is landline phone)
Suppose I am testing a web base health care insurance software and I am working in the member portal. Could anyone please give me some example of some common/critical bugs/defects to be found in this software testing process ?
What would be a good answer when someone asks 'What was your best bug you found'? How does a person know whats the best bug? I never found the best bug..all my bugs are good.
What test strategy followed in your project?
The difference between Testing and Quality Assurance. Basic Difference in the Job profile Job profile
If a bug is found at the time of release.what you do?
What is boundary testing?