top button

When to stop testing? (Or) How do you decide when you have tested enough?

–2 votes
posted Feb 6 by Arun

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

2 Answers

0 votes

There are many factors involved in the real-time projects to decide when to stop testing.

  • Testing deadlines or release deadlines
    By reaching the decided the pass percentage of test cases
    The risk in the project is under the acceptable limit
    All the high priority bugs, blockers are fixed
    When acceptance criteria are met

As per ISTQB, It depends on the risks for the system being tested.

Here I am going to conclude the post “Software Testing Interview Questions”. Final words, Bookmark this post “100 Software Testing Interview Questions” for future reference. After reading this post, if you find that we missed some important questions, please comment below we would try to include those with answers.

Here I have hand-picked a few posts which will help you to learn more interview related stuff:

Why You Choose Software Testing As A Career

Software Testing as a career – why I chose?

A simple answer is I love to be a Software Tester. So, I chose Software Testing as a career. I would like to mention a few more points why I love to be a Software tester and chose Software Testing as a career.

I love solving logical puzzles. Testing is kind of solving a logical puzzle. We will be given a software which will go straight to the market if we nod our head that there are no bugs in the software and ready to release. We, the Testers are the protectors at the gateway. We not only find the bugs. We break the system too in terms of stress testing.

I love helping others.

answer Feb 6 by Arunkumaarts
0 votes

Stopping a testing phase (Or) when to stop testing the application are determined with various aspects. A product is built and enhanced based on the customer's needs and requirements. So the software companies encourage their customers to provide a valuable feedback about their software and there are few customer who provide the honest review about the software and if that review contents any new idea/ suggestion or requirement, based on the business use case the product management team member will take call whether or not to include the new idea or product behavior change.

If the PM (Product Management) team decided to include the idea given by their customers then that ideas are developed and implemented in software and before releasing the update to market, the new ideas are sent for the end to end testing process and in this testing phase the QA Testers are suppose to perform an intense test and find as many as bugs possible to ensure that this bugs are addressed before releasing the update to market. In this phase although the end to end testing is put on pause, however if the customer revert stating that, the found few issues/ error then the testing process is reinstated to ensure that those issues/error are addressed by the concern team members.

answer 3 days ago by Vinod Kumar