There are ways to avoid running all night, which I assume is a side-effect of combinatoric explosion of the test space. Check out pairwise (a.k.a. "all pairs")

There are ways to avoid running all night, which I assume is a side-effect of combinatoric explosion of the test space. Check out pairwise (a.k.a. "all pairs") testing: https://en.wikipedia.org/wiki/All-pairs_testing https://en.wikipedia.org/wiki/All-pairs_testing https://www.pairwise.org https://www.pairwise.org And there are also ways to (at runtime) prune the set of cases being run based on system behavior. As in "aha - these similar things failed to meet expectations in the same way, let's flag it as the same bug and stop running anything with the failure characteristic," if that makes sense. Say, for example, you have a zip code field that takes a string and after several instances of tests with a zip code your test determines that you're getting a NaN error (for a string field?) . . . stop running any tests with zip code strings and treat all of those as the same failure. This can greatly increase test speed and make triage of failures easier.