The application of multiple condition testing is also being considered. Which specification-based technique is largely based on the principle of multiple condition testing? 1 credit [K2]

Question

Options

• AEquivalence Partitioning
• BState Transition Testing
• CDecision Table Testing
• DUse Cases

• B
  3% (1)
• C
  93% (37)
• D
  5% (2)

Explanation

Decision Table Testing is correct because it explicitly models all combinations of input conditions (true/false) against expected actions or outputs. Each column in the decision table represents a unique combination of conditions, making it the specification-based technique that most directly implements the principle of multiple condition testing.

Why the distractors are wrong:

• A (Equivalence Partitioning): Groups inputs into partitions where each value behaves equivalently - it tests representative single values, not combinations of conditions.
• B (State Transition Testing): Focuses on how a system moves between states in response to events over time; it models behavior sequences, not condition combinations.
• D (Use Cases): Describes user interactions and functional flows from a user's perspective; it has no systematic mechanism for combining conditions.

Memory tip: Think of a decision table like a truth table from logic - every column is a unique combination of condition values (T/F), so "multiple conditions + table = Decision Table Testing." If you see the phrase combinations of conditions, the answer is almost always Decision Table Testing.

No community discussion yet for this question.