Reviewing Decision Tables: Consistency, Completeness and Overlapping Rules

Reviewing Decision Tables: Consistency, Completeness and Overlapping Rules (ISTQB CTAL-TA)

Introduction
In the ISTQB Certified Tester Advanced Level Test Analyst (CTAL-TA) syllabus, decision table testing is one of the rule-based test techniques. A decision table is a tool for designing tests. It is also a powerful static analysis and review tool. When a Test Analyst builds or reviews a decision table, they can find defects in the specification before any code is run. Three properties are central to that review: completeness, consistency and the absence of harmful overlapping rules. This guide covers what these properties mean, why they matter, how to check them step by step, and how to answer exam questions about them.

1. Why It Is Important
Requirements defects are cheap to fix early. Business rules are often written in natural language, such as 'Members get 15% off orders over 100'. Prose like this easily hides gaps and contradictions. Putting the rules into a table exposes them, which is a classic example of shift-left quality assurance.
Missing rules cause undefined behaviour. If a combination of conditions has no rule, developers will guess the outcome. Testers then have no expected result, so the test oracle is missing.
Contradictory rules cause unpredictable systems. If two rules apply to the same situation but prescribe different actions, the system's behaviour depends on implementation order. This creates intermittent or disputed defects.
Redundant rules waste effort and confuse maintenance. Duplicate rules are less dangerous. However, they inflate the test suite and can become contradictions after a later change.
Coverage depends on it. Decision table coverage is measured against the feasible columns. If the table is incomplete or inconsistent, the coverage measure is meaningless.

2. What It Is: Key Concepts
Decision table structure

• Conditions are the inputs or states that influence the decision, shown in the upper rows.
• Actions are the outcomes the system must perform, shown in the lower rows.
• Rules (columns) each describe one combination of condition values and the resulting actions.

Notation used in the syllabus

• T/F or Y/N are values for Boolean conditions. Conditions can also have more than two values (extended-entry tables), such as Low/Medium/High.
• - (dash) means the condition is irrelevant to this rule ('don't care'). The rule applies whatever the condition's value is.
• N/A means the condition is infeasible or not applicable for this rule.
• X (or T) in an action row means the action occurs. A blank (or F) means it does not.

Full versus collapsed tables

• A full table lists every combination of conditions. For n Boolean conditions this means 2^n columns. In general it means the product of the number of values of each condition.
• A collapsed (minimised) table merges columns whose actions are the same and where one condition does not affect the outcome. The merged condition becomes a dash.
• Collapsed tables are compact. They are also the place where overlaps and gaps typically creep in.

The three review properties
Completeness

• Every feasible combination of condition values is covered by at least one rule.
• A missing combination means the specification is incomplete.

Consistency (no contradictions)

• No two rules that can apply to the same combination of conditions prescribe different actions.
• If they do, the table is inconsistent, also called contradictory.

Overlapping rules

• Two or more rules overlap when at least one combination of condition values satisfies all of them. This usually happens because of dashes.
• If overlapping rules have identical actions, the overlap is redundancy. This is not strictly wrong, but it should be cleaned up.
• If overlapping rules have different actions, the overlap is a contradiction. This is a genuine defect.

The ideal reviewed table

• Every feasible combination of conditions is matched by exactly one rule.
• Zero matches means incomplete.
• Two or more matches means overlapping, which is either redundant or contradictory.

3. How It Works: Reviewing a Table Step by Step
Step 1: Identify conditions and their possible values. Count the values of each condition and multiply them to get the total number of combinations. For example, 3 Boolean conditions give 2 x 2 x 2 = 8 combinations. Two Boolean conditions plus one condition with 3 values give 2 x 2 x 3 = 12.
Step 2: Remove infeasible combinations. Some combinations cannot occur in reality. For example, 'Age < 18' and 'Age > 65' cannot both be true. Exclude them, documenting them as N/A. What remains is the total number of feasible combinations.
Step 3: Expand each rule into the combinations it covers. Each dash multiplies coverage by the number of values of that condition. For Boolean conditions, a rule with k dashes covers 2^k combinations.
Step 4: Check completeness. List the feasible combinations not covered by any rule. A quick heuristic is to sum the combinations covered by all rules:

• If the sum is less than the feasible total, the table is definitely incomplete.
• If the sum is greater, there is definitely overlap.
• If the sum is equal, the table may still contain both a gap and an overlap that cancel each other out. Always confirm by listing the combinations.

Step 5: Check for overlaps. Find any combination covered by more than one rule. For each overlap, compare the actions:

• The same actions mean the rules are redundant.
• Different actions mean the rules are contradictory.

Step 6: Report and resolve.

• Raise the issues found with the business analyst or product owner. The tester does not decide business rules.
• Gaps need new rules.
• Contradictions need a decision about which action is correct. Sometimes the fix is to add a condition value instead of a dash.
• Redundancies can be merged.

Worked Example
Conditions: C1 = Loyalty member? C2 = Order over 100? C3 = Has coupon? These give 8 combinations in total.

	R1	R2	R3	R4
C1	Y	Y	N	-
C2	Y	N	-	Y
C3	-	Y	Y	N
Action	15% discount	10% discount	5% discount	Free shipping only

Expansion of each rule:

• R1 covers YYY and YYN (2 combinations).
• R2 covers YNY (1 combination).
• R3 covers NYY and NNY (2 combinations).
• R4 covers YYN and NYN (2 combinations).

Sum check: 2 + 1 + 2 + 2 = 7 matches against 8 combinations.
Overlap: YYN is matched by both R1 (15% discount) and R4 (free shipping only). The actions differ, so this is a contradiction and the table is inconsistent.
Gaps: Because of the overlap, only 6 distinct combinations are covered. The missing combinations are YNN (member, small order, no coupon) and NNN. The table is incomplete.
Conclusion: There are three findings to raise:

• One contradiction (YYN).
• Two missing rules (YNN and NNN).
• A clarification about whether R1 and R4 were meant to be combined, for example a discount plus free shipping.

Relation to Test Design and Coverage

• Once the table has been reviewed and corrected, each feasible column normally becomes at least one test case.
• Decision table coverage = number of exercised feasible columns divided by total feasible columns, expressed as a percentage.
• Collapsed columns reduce the number of tests. The trade-off is that a defect hidden in a 'don't care' condition may be missed. Test Analysts may choose to test some expanded combinations when risk justifies it.
• Infeasible combinations are excluded from the coverage denominator.

4. Common Pitfalls

• Forgetting that a dash expands to all values. With a 3-valued condition, one dash triples coverage, not doubles it.
• Treating every overlap as an error. Redundancy with identical actions is a quality issue, not a contradiction.
• Counting infeasible combinations as missing rules.
• Relying only on the sum check. A gap and an overlap can cancel each other out.
• Confusing an N/A condition (infeasible) with a dash (irrelevant).

Exam Tips: Answering Questions on Reviewing Decision Tables: Consistency, Completeness and Overlapping Rules

Tip 1: Learn the definitions precisely.

• Incomplete means a feasible combination has no rule.
• Inconsistent/contradictory means overlapping rules give different actions.
• Redundant means overlapping rules give the same actions.

Many distractors swap these terms.

Tip 2: Always compute the total first.

• Multiply the number of values of each condition. Write the number down.
• Then subtract any combinations the question states are impossible.

Tip 3: Expand dashes systematically.

• On scratch paper, list every combination as a string, such as YYN. Tick off which rule or rules match each one.
• A combination with no ticks is a gap. A combination with two or more ticks is an overlap.
• This takes about two minutes and is far more reliable than intuition.

Tip 4: Use the sum shortcut only as a first signal.

• A sum below the total proves incompleteness.
• A sum above the total proves overlap.
• A sum equal to the total proves nothing. Verify by listing.

Tip 5: Read the question stem carefully.
Look for wording such as 'Which combination is NOT covered?', 'Which two rules contradict?', 'How many test cases for 100% decision table coverage?' or 'Which statement BEST describes the problem?'. A table can be both incomplete and inconsistent. Choose the answer that addresses exactly what is asked.

Tip 6: Count coverage against feasible columns.

• For coverage questions, the minimum number of tests usually equals the number of feasible columns in the (corrected) table.
• Infeasible columns are not counted.

Tip 7: Know the tester's role.

• When asked what the Test Analyst should do on finding a contradiction or gap, the correct answer is usually to report it and seek clarification from stakeholders or the business analyst.
• It is not to decide the business rule themselves or to pick one rule arbitrarily.

Tip 8: Recognise the benefits stated in the syllabus.

• Decision tables help identify all combinations of conditions.
• They find gaps and contradictions in requirements.
• They support both static testing (reviews) and dynamic test design.

A limitation is the exponential growth of combinations as the number of conditions increases. This is why minimisation, and risk-based selection of combinations, are used.

Tip 9: Watch for extended-entry conditions.
If a condition has three values, such as Gold/Silver/Bronze, a dash in that row covers 3 combinations. Exam writers like this trap.

Tip 10: Eliminate distractors logically.

• If an option claims a contradiction between two rules that differ on a non-dash condition value (for example, one has Y and the other has N in the same row), those rules can never overlap. Reject the option.
• Two rules overlap only if, in every condition row, their values are equal or at least one of them is a dash.

Quick Overlap Test (memorise this)
Rules A and B overlap only if, for every condition, A = B, or A = '-', or B = '-'. If they overlap, compare the actions:

• Same actions mean the rules are redundant.
• Different actions mean the rules are contradictory.

Summary
Reviewing a decision table means confirming that every feasible combination of conditions is matched by exactly one rule. Missing combinations mean the table is incomplete. Overlapping rules with different actions mean it is inconsistent. Overlapping rules with the same actions are redundant. In the exam:

• Calculate the total number of combinations.
• Expand the dashes.
• Tick off each combination against the rules.
• Map your findings to the precise terminology before choosing an answer.