Part 1: Decision table testing
A Typical Structure of a Decision Table
Why use decision tables
Equivalence partitioning and boundary value analysis tend to be more focused on the user interface.
The other two specification-based techniques, decision tables and state transition testing are more
focused on business logic or business rules.
Definition
Steps to Create a decision table
1. List All Stub Conditions
2. Calculate the Number of Possible Combinations (Rules)
3. Place all of the Combinations into the Table
4. Reduce test combinations
5. Check covered combinations
6. Fill the Table with the Actions
Step 1: List All Stub Conditions (Causes)
Hints:
Write down the values the cause/condition can assume
Cluster related causes
Put the most dominating cause first
Put multi valued causes last
Step 2: Calculate combinations
Step 3: Place all of the Combinations into the
Step 4: Reduce combinations
Step 5: Check covered combinations
Step 6: Fill the Table with the Effects (Actions)
Sample: Specification Create a decision table
Step One – List All Stub Conditions
The condition stubs for the table would be:
• a, b, c form a triangle?
• a = b?
• a = c?
• b = c?
Step Two – Calculate the Number of Possible
Combinations (Rules)
• Number of Rules = 2Number of Condition Stubs
• So therefore, Number of Rules = 24 = 16
Step Three&Four – Place all of the Combinations into the Table and reduce the combinations
Step Five – Check Covered Combinations
• This step is a precautionary step to check for errors and redundant and inconsistent rules.
Step Six – Fill the Table with the Actions
Decision Table for the Triangle Problem
