Decision table testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a decision table as a list of dictionaries.

Testing Fundamentals

decision_table = [[1]]

Drag options to blanks, or click blank then click option'

A'condition: A, action: X'

B{'condition': 'A', 'action': 'X'}

C('condition', 'A', 'action', 'X')

D['condition', 'A', 'action', 'X']

Attempts:

3 left

💡 Hint

Common Mistakes

Using tuples or lists instead of dictionaries for rules.

The decision table is best represented as a list of dictionaries where each dictionary maps conditions to actions.

2fill in blank

medium

Complete the code to check if a condition matches in the decision table.

Testing Fundamentals

if rule['condition'] == [1]:
    execute_action(rule['action'])

Drag options to blanks, or click blank then click option'

Aaction

Brule

C'A'

Dcondition

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names instead of string literals.

We compare the condition value in the rule to the string 'A' to find matching rules.

3fill in blank

hard

Fix the error in the code to iterate over all rules in the decision table.

Testing Fundamentals

for rule in [1]:
    print(rule['action'])

Drag options to blanks, or click blank then click option'

Adecision-table

BdecisionTable

Cdecision_table()

Ddecision_table

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses like a function call.

Using invalid variable names with hyphens.

The decision table is a list named 'decision_table'. We iterate over it directly without parentheses or hyphens.

4fill in blank

hard

Fill both blanks to create a decision table filtering rules with condition 'B'.

Testing Fundamentals

filtered_rules = [rule for rule in decision_table if rule[[1]] == [2]]

Drag options to blanks, or click blank then click option'

A'condition'

B'action'

C'B'

D'Y'

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping keys and values.

Using wrong string literals.

We filter rules where the 'condition' key equals 'B'.

5fill in blank

hard

Fill all three blanks to create a decision table dictionary comprehension with conditions and actions.

Testing Fundamentals

decision_dict = { [1]: [2] for rule in decision_table if rule[[3]] == 'C'}

Drag options to blanks, or click blank then click option'

Arule['condition']

Brule['action']

C'condition'

D{rule['condition']}

Attempts:

3 left

💡 Hint

Common Mistakes

Missing curly braces for dict comprehension.

Swapping keys and values.

The dictionary comprehension uses curly braces to create a dict with condition keys and action values, filtering rules where condition is 'C'.

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