Decision table testing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Decision Table Conditions

In decision table testing, what does each condition in the table represent?

A A user interface element

B A possible input or state that affects the system's behavior

C A bug found during testing

D A test case that must be executed

💡 Hint

Think about what influences the decisions in the system.

Each condition in a decision table represents an input or state that influences how the system behaves. These conditions combine to define different scenarios.

❓ Predict Output

intermediate

Output of Decision Table Test Case Count

Given a decision table with 3 conditions each having 2 possible values (True/False), how many unique test cases does the table represent?

A 8

B 6

C 9

D 12

💡 Hint

Calculate the total combinations of all conditions.

Each condition has 2 values, so total test cases = 2 * 2 * 2 = 8.

❓ assertion

advanced

Correct Assertion for Decision Table Coverage

Which assertion correctly verifies that all decision table rules have been tested?

Testing Fundamentals

tested_rules = {1, 2, 3, 4}
all_rules = {1, 2, 3, 4}
# Which assertion below is correct?

A assert tested_rules == all_rules

B assert tested_rules != all_rules

C assert tested_rules < all_rules

D assert tested_rules > all_rules

💡 Hint

Think about what it means to have tested all rules.

To confirm all rules are tested, the sets must be exactly equal.

🔧 Debug

advanced

Identify the Error in Decision Table Test Code

What error will this Python code raise when checking decision table rules coverage?

Testing Fundamentals

all_rules = {1, 2, 3, 4}
tested_rules = [1, 2, 3, 4]
assert tested_rules == all_rules

A TypeError: unsupported operand type(s) for ==: 'list' and 'set'

B No error, assertion passes

C AssertionError

D TypeError: unhashable type: 'list'

💡 Hint

Check the types of variables compared.

Comparing a list and a set with == returns False but does not raise an error. However, the assertion fails causing AssertionError, not TypeError. So check carefully.

❓ framework

expert

Best Practice for Automating Decision Table Tests

Which approach best automates testing all rules in a decision table using a test framework?

A Use random inputs in a single test function without mapping to rules

B Write separate test functions manually for each rule without loops

C Test only the most common rule and skip others

D Write one test function with a loop that iterates over all rule inputs and asserts expected outputs

💡 Hint

Think about maintainability and coverage.

Using a loop over all rules in one test function ensures all rules are tested systematically and code is easy to maintain.

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