For equivalence partitioning based on this specification, how many output classes can be determined? 2 credits [K3]

Question

Options

• A2
• B3
• C4
• D5

• A
  8% (4)
• B
  77% (40)
• C
  4% (2)
• D
  12% (6)

Explanation

Option B (3) is correct because equivalence partitioning on a typical range-based specification yields three output classes: one valid class (values within the acceptable range) and two invalid classes (values below the lower boundary and values above the upper boundary). Each class represents a distinct behavior, so combining both invalid cases into one would lose meaningful distinctions.

Option A (2) is wrong because it collapses the two invalid output classes - "below range" and "above range" - into a single partition, losing the behavioral distinction between them. Options C (4) and D (5) over-partition by creating more classes than the specification actually supports; without additional defined sub-ranges or conditions in the spec, there is no basis for splitting beyond three classes.

Memory tip: Think "below / within / above" - any range-based spec almost always produces exactly 3 output partitions by default. If you see a simple min–max boundary in a spec with no extra conditions, anchor on 3.

No community discussion yet for this question.