Testing teams often drown in an ocean of possible inputs. Two classic techniques—Equivalence Partitioning (EP) and Boundary Value Analysis (BVA)—let you pick representative values that still exercise every logical path. Below is a quick guide to applying them together, with a concrete example and practical do‑and‑avoid tips.
What is EP
- Split input into classes – Group inputs that should behave the same way. For a numeric field, any value below the lower limit, any value inside the allowed range, and any value above the upper limit form separate equivalence classes.
- Test one value per class – One representative value stands in for the whole group. If the class is “valid”, any value inside it should pass; if the class is “invalid”, any value should trigger the same error handling.
What is BVA
- Test the edges – Bugs tend to cluster at boundaries rather than in the middle of a range. Checking the limits reveals off‑by‑one errors, rounding problems, and incorrect comparison operators.
-
Min, min+1, max, max‑1 – The four values that catch most boundary defects. For an inclusive range
[min, max], test the exact limits and the values just inside the limits.
Worked Example
Imagine a form field that accepts ages from 18 to 60 inclusive.
| Equivalence class | Representative test value |
|---|---|
< 18 (invalid) |
17 |
18–60 (valid) |
30 |
> 60 (invalid) |
61 |
Applying BVA adds the four boundary values:
- Min: 18 – should be accepted.
- Min + 1: 19 – also accepted, confirming the lower edge works.
- Max: 60 – should be accepted.
- Max ‑ 1: 59 – accepted, confirming the upper edge works.
Together, the test set becomes {17, 18, 19, 30, 59, 60, 61}. It covers all valid and invalid partitions while focusing on the most error‑prone points.
Where It Fits
- Use during test design – Apply EP and BVA while you are writing test cases, before any code is executed. This front‑loading reduces the number of tests you need to create later.
- Pairs with decision tables – When inputs involve combined conditions (e.g., age and membership level), EP defines the partitions for each dimension, and decision tables help you map the cross‑product of those partitions into a manageable set of test scenarios.
Do / Avoid
Do
- Document which class each test case represents, so reviewers can see the rationale behind every value.
- Combine EP with BVA for tighter coverage; the boundary tests are simply the edge members of each equivalence class.
- Apply the techniques to both valid and invalid input ranges to verify positive and negative paths.
Avoid
- Don’t test every value in a class; one well‑chosen representative is enough.
- Don’t skip invalid partitions; they are essential for confirming robust error handling.
- Don’t treat boundaries as optional edge cases; they are the most likely places for defects.
Use EP to slice the input space and BVA to probe its edges—together they give you maximum confidence with minimal test effort.
Top comments (0)