Exhaustive Testing

Go back to Tutorial

Exhaustive Testing

Exhaustive Testing

Combinations of Input and preconditions show that the number of faults in a software product can be very large. Moreover, defects occurring rarely are difficult to find in testing. In this section, we will learn about exhaustive testing along with why is it impractical and impossible.

Exhaustive testing also referred to as complete testing takes place when all the testers in your team are worn-out. Moreover, it is a quality assurance testing technique in which all data are put to the test. However, it is not possible to test everything (all combinations of inputs and preconditions) except for minor cases.

Why Is It Impractical and Impossible

It is not possible to run complete testing. Therefore, for most systems, it is impossible because of the following reasons:

  • Firstly, the domain of possible inputs of a program is too large to be completely used in testing a system.
  • Secondly, there may be timing constraints on the inputs. That is to say, an input may be valid at a certain time and invalid at other times.
  • Thirdly, design issues may be a fusion to completely test. For instance, a programmer may use a global variable or a static variable to control program execution.
  • Above all, it’s not feasible to create all possible execution environments of the system. Further, this becomes more essential when the behavior of the software system depends on the real and outside world.

 

Get certified and unlock more opportunities. Practice and Validate your skills to become a Certified Manual Tester Now!

Go back to Tutorial

Share this post
[social_warfare]
Learning Web APIs
Static versus Dynamic Testing

Get industry recognized certification – Contact us

keyboard_arrow_up