What is Equivalence partitioning?

A black-box testing technique that divides the inputs into groups that the program should handle in the same way (equivalence classes) and tests one representative value from each class. Both valid classes of accepted inputs and invalid classes of inputs that should cause an error are chosen.

Japanese name: 同値分割

Equivalence partitioning appears in 2 practice questions across 1 topic, including Software Development and Project Management.

Field: Software Development and Project Management

Try it: questions about Equivalence partitioning

An input field accepts only integers; values from 1 to 100 inclusive are accepted and all others cause an error. When the input is divided by equivalence partitioning, how many equivalence classes are there in total (valid and invalid classes combined)?

  1. A1
  2. B2
  3. C3
Show answer and explanation

Answer: C. 3

Equivalence partitioning divides the inputs into groups (equivalence classes) that the program should handle in the same way, and tests one representative value from each class. For this field there is one valid class (1 to 100) and two invalid classes (0 or less, and 101 or more), giving 3 in total. Choosing, for example, 50, −5 and 150 as representatives checks every class with three tests. The invalid inputs are split into a low side and a high side because the program handles them with separate checks (the lower-limit check and the upper-limit check).

Equivalence partitioning in the explanations

Questions that mention Equivalence partitioning (2)

  1. An input field accepts only integers; values from 1 to 100 inclusive are accepted and all others cause an error. When the input is divided by equivalence partitioning, how many equivalence classes are there in total (valid and invalid classes combined)?
  2. Which describes black-box testing?

Books on Software Development and Project Management Ad

As an Amazon Associate I earn from qualifying purchases.

Related terms

Black-box testing Boundary value analysis White-box testing Agile development Branch coverage CI/CD (continuous integration and continuous delivery) Critical path method (CPM) Earned value management (EVM) Scrum SLA (service level agreement)

Back to the glossary