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.