Decision table testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Decision Table Testing?

Decision Table Testing is a black-box test design technique that uses a table to represent combinations of inputs and their corresponding outputs or actions. It helps ensure all possible scenarios are tested.

beginner

What are the main parts of a decision table?

A decision table has four main parts: Conditions (inputs), Condition Alternatives (possible values for each condition), Actions (outputs), and Action Entries (which actions to take for each condition combination).

beginner

Why is Decision Table Testing useful?

It helps testers systematically cover all combinations of inputs, especially when many conditions affect the outcome. This reduces missing important test cases and improves test coverage.

intermediate

How do you handle 'Don't Care' conditions in decision tables?

A 'Don't Care' condition means the value of that condition does not affect the outcome for that rule. It is marked with a dash (-) and helps reduce the number of test cases by grouping similar scenarios.

beginner

Give a simple example of a decision table for a login system with conditions: Username valid, Password valid.

Conditions: Username valid (Yes/No), Password valid (Yes/No). Actions: Allow login, Show error. Example rules: 1) Yes/Yes -> Allow login, 2) Yes/No -> Show error, 3) No/Yes -> Show error, 4) No/No -> Show error.

What does a decision table primarily help with in testing?

A Measuring test execution speed

B Organizing input conditions and expected outputs systematically

C Writing code for automated tests

D Designing user interfaces

Decision tables organize input conditions and expected outputs to cover all combinations systematically.

In a decision table, what does a dash (-) usually represent?

A A mandatory condition

B An action to perform

C An error in the table

D A 'Don't Care' condition

A dash (-) means the condition value does not affect the outcome for that rule, called 'Don't Care'.

Which part of a decision table lists the possible values for each condition?

A Condition Alternatives

B Actions

C Action Entries

D Test Scripts

Condition Alternatives are the possible values each condition can take.

Decision table testing is best suited for testing scenarios with:

A Single input and output

B Performance under load

C Multiple conditions affecting outcomes

D Only user interface elements

It is ideal when multiple conditions influence the result, to cover all combinations.

What is the main goal of using decision tables in testing?

A To ensure all possible input combinations are tested

B To reduce the number of test cases by ignoring some conditions

C To automate test execution

D To write code faster

Decision tables help ensure all input combinations are tested for thorough coverage.

Explain how decision table testing helps improve test coverage.

Think about how organizing inputs and outputs in a table helps testers.

Describe the structure of a decision table and the role of each part.

Focus on the four main parts and what they represent.

Practice

1. What is the main purpose of decision table testing in software testing?

easy

A. To improve software performance

B. To write code faster

C. To design user interfaces

D. To organize conditions and actions to cover all possible cases

Solution

1. Step 1: Understand decision table testing basics

   Decision table testing helps testers list all conditions and their possible actions systematically.

2. Step 2: Identify the main goal

   The goal is to cover all possible combinations of conditions to avoid missing or conflicting rules.

3. Final Answer:

   To organize conditions and actions to cover all possible cases -> Option D

4. Quick Check:

   Decision table = organize all cases [OK]

Hint: Think of decision tables as a checklist for all condition combos [OK]

Common Mistakes:

• Confusing decision tables with performance testing
• Thinking it is about coding speed
• Mixing it up with UI design

2. Which of the following is the CORRECT way to represent a condition in a decision table?

easy

A. Writing long paragraphs explaining the condition

B. Using 'Yes' or 'No' to show condition states

C. Using random numbers without meaning

D. Ignoring conditions and only listing actions

Solution

1. Step 1: Review how conditions are shown in decision tables

   Conditions are usually shown as simple states like 'Yes' or 'No' to keep clarity.

2. Step 2: Eliminate incorrect options

   Long paragraphs or random numbers confuse the table. Ignoring conditions defeats the purpose.

3. Final Answer:

   Using 'Yes' or 'No' to show condition states -> Option B

4. Quick Check:

   Conditions = Yes/No states [OK]

Hint: Use simple states like Yes/No for conditions in tables [OK]

Common Mistakes:

• Writing detailed text instead of simple states
• Using meaningless numbers
• Skipping conditions entirely

3. Given the decision table below, what is the expected action if Condition A = No and Condition B = Yes?

Condition A	Condition B	Action
Yes	Yes	Action 1
Yes	No	Action 2
No	Yes	Action 3
No	No	Action 4

medium

A. Action 3

B. Action 1

C. Action 2

D. Action 4

Solution

1. Step 1: Locate the row matching Condition A = No and Condition B = Yes

   Check the table row where Condition A is 'No' and Condition B is 'Yes'.

2. Step 2: Identify the corresponding action

   The matching row shows 'Action 3' as the action.

3. Final Answer:

   Action 3 -> Option A

4. Quick Check:

   Conditions No/Yes = Action 3 [OK]

Hint: Match conditions row to find the correct action quickly [OK]

Common Mistakes:

• Mixing up Yes/No order
• Choosing action from wrong row
• Ignoring one condition

4. A tester created a decision table but missed one condition combination. What is the likely problem caused by this mistake?

medium

A. All conditions are tested anyway

B. The software will run faster

C. Some test cases will be missing, causing incomplete testing

D. The decision table will have duplicate rows

Solution

1. Step 1: Understand the impact of missing condition combinations

   Missing a condition combo means that scenario is not tested.

2. Step 2: Identify the consequence

   Incomplete testing can let bugs slip through because not all cases are covered.

3. Final Answer:

   Some test cases will be missing, causing incomplete testing -> Option C

4. Quick Check:

   Missing combos = incomplete tests [OK]

Hint: Missing combos mean missing tests, not faster software [OK]

Common Mistakes:

• Thinking missing combos speed up software
• Assuming all conditions tested anyway
• Confusing missing combos with duplicates

5. You have a system with three conditions: C1, C2, and C3, each can be Yes or No. How many unique rules (rows) should a complete decision table have to cover all combinations?

hard

A. 8

B. 12

C. 9

D. 6

Solution

1. Step 1: Calculate total combinations for three binary conditions

   Each condition has 2 states (Yes/No). Total combinations = 2 * 2 * 2 = 8.

2. Step 2: Understand decision table rows

   Each unique combination corresponds to one rule (row) in the decision table.

3. Final Answer:

   8 -> Option A

4. Quick Check:

   2^3 = 8 rules needed [OK]

Hint: Use 2^number_of_conditions for total rules [OK]

Common Mistakes:

• Adding conditions instead of multiplying
• Using wrong powers (like 3^2)
• Confusing rules with actions