Why do test suites with the same coverage level have different numbers of steps?
This is due to a couple of factors. First, Tester employs a random number generator to select some inputs. Also, Tester includes a “pruning” phase during which test steps that do not improve coverage are eliminated. So even though two different test suites may achieve the same level of coverage, they could be quite different.
Related Questions
- How do I quickly do analyses using different parameters like changing the mask or selecting different numbers for data-reduction steps with the same functional data?
- Can each container be a different Solaris patch level, so I can test patches in a "test" container before applying them to a "production" container?
- Why do test suites with the same coverage level have different numbers of steps?
