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.