What are the exit criteria in software testing?

What are the exit criteria in software testing? where I would to stop the testing.
TestOrigen Software Services Pvt. Ltd.Digital Marketing ExecutiveAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

That probably varies by the software being tested.  However, in general terms...

What is the software supposed to do?  Were you able to show that it did that?  What happens if you go outside the flow and try and enter in erroneous data?  Does the software allow that and if so, what were the consequences. Test as many features as possible; even those that you don't think you'd use. Test with as many other applications as you'd think would be on the same machines and test with as many different hardware types and OS versions as necessary. Depending on the specifics of the software being tested, the hardware requirement may not be as critical as long as the resources for memory and CPU are met.

You can't test everything and every possible scenario.  But once you've done what you feel is your cure diligence, I'd call it done and let the chips fall where they may.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David FavorLinux/LXD/WordPress/Hosting SavantCommented:
To expand on what jhyiesla said.

1) Some tests have a prerequisite chain. In other words, if test 5 of 10 tests fail + you know test 6-10 depend on test 5 passing, then testing stops at this point.

2) Other tests a non-dependent. For example, you might run a test over 1000 lines of a PDF document to determine if you're parser recognizes every line. In this case you might have 10 tests, which apply to all 1000 lines. For this type of test, normally I accumulate all errors, then at end of test run, sort all accumulated tests into unique failures + then only emit a summary of test failures. This allows the parser to be modified to catch all new record variations.

In #2, if you abort your test suite each time an exception is raised, then debugging + code fixing becomes very long.

My guideline - create a test suite, which fastest debug + fix of the code base being tested.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.