One and Only One Definition
In the set of A,B,C... one and only one may be true, but never all false; thus, there will always be just one true.
A user wants to maintain accounts for various types of customers.
When a user enters that account maintenance system, he/she selects what type of maintenance activity to do.
The user can do one and only one activity at a time for any account.
Who are the actors for our story?
- User: The object selecting the account to maintain
- Account: The object being maintained
What are the test cases necessary to define in order to cover all exit points?
- Add Corporate Account - The user wants to add a corporate account.
- Modify Corporate Account - The user wants to modify a corporate account.
- Delete Corporate Account - The user wants to delete a corporate account.
- Add Government Account - The user wants to add a government account.
- Modify Government Account - The user wants to modify a government account.
- Delete Government Account - The user wants to delete a government account.
- Add Retail Account - The user wants to add a retail account.
- Modify Retail Account - The user wants to modify a retail account.
- Delete Retail Account - The user wants to delete a retail account.
Variables & States
What are the variables needed to check our test cases, and for each variable, what states are needed?
- add Corporate account
- add Government Account
- add Retail Account
- modify Corporate account
- modify Government Account
- modify Retail Account
- delete Corporate account
- delete Government Account
- delete Retail Account
GenRocket Pairwise Configuration
Pairwise Test Case Variables
Pairwise Variable - addAccount
Pairwise Variable - deleteAccount
Pairwise Variable - modifyAccount
Pairwise Test Case Constraints
This one inclusive constraint covers all three test cases.