Automated Test Design
Goal: Apply business-related rules to combinatorial methods to avoid repetitive, cost-ineffective, and manual maintenance of automatically-generated test sets.
Let’s face it: Nothing is perfect. Life is messy, outcomes are uncertain, people are irrational, and relations (especially in test case design) are complex.
As you might have already experienced, even small test sets are often overloaded with countless business-related dependencies between attributes and instances. Well, the number (and nature) of these dependencies aren’t necessarily so troubling during the initial test case creation because business experts are often supporting you at that point. However, if these business experts move on, this knowledge also moves on. As a result, the maintenance of even a small set of test cases becomes a complex when information must be added, deleted, or somehow modified due to some change in the application or business logic.