SoftwareTestPilot

Turn one input rule into a small, strong set of test cases. Simulated in your browser, free, no sign-in.

Boundary Values & Equivalence Partitioning

Step 1 of 6

Now simulating · step 1 of 6

Read the rule

Paused
Rule: Age must be 18 to 60

Press Next to split the range into partitions.

Tip: click a coloured area or an edge line to see what it does.

Text description of this step
  • Rule: ages 18 to 60 are accepted.
Speed

Keyboard: Space plays or pauses (when not typing).

Learning objective: Design a small test set from one input rule, and prove that boundary values catch defects that middle values miss.

Step 1 · Beginner

Read the rule

A sign-up form has an Age field. It accepts ages 18 to 60. Anything else should show an error. First we turn this sentence into a range with clear edges.

Expected outcome: You can say in one line which ages are accepted.

Two techniques, not one

  • Equivalence partitioning groups inputs the system should treat alike and tests one value per group. Invalid formats (empty, letters, decimals) are their own partitions, separate from numbers that are too low or too high.
  • Boundary value analysis tests at the edges of ordered partitions. The 2-value version tests each edge and its outside neighbour; the 3-value version adds the inside neighbour. Books and teams use both, so name the one you mean.
Common mistakes
  • Testing only the edges and forgetting one value inside each partition.
  • Mixing invalid formats into the 'below range' partition. A blank field is not a small number.
  • Saying BVA 'always' uses six values without naming 2-value or 3-value.
  • Claiming the set gives complete coverage. It only covers the rules you modelled.
  • Not asking whether the range is inclusive before writing tests.
About this lesson

You will learn to

  • Split an input rule into valid and invalid partitions.
  • Pick boundary values on and around each edge.
  • Explain why a boundary value catches bugs a middle value misses.

Before you start

  • Know what a test case is (input, expected result).

Your progress on this topic

Explored
0 of 6 guided steps viewed
Practiced
  • Not yet: Run at least 3 test values of your own
  • Not yet: Run a test value against a build with a planted bug
Challenges passed
  • Beginner: 0 of 2 · hints 0 · wrong answers 0
  • Practitioner: 0 of 2 · hints 0 · wrong answers 0
  • Advanced: 0 of 2 · hints 0 · wrong answers 0

Watching the walkthrough only counts as explored. Practice needs you to use the lab yourself, and a challenge passes only when your answer meets its criteria.

Practise more

Intentional failure: Planted bug: the maximum age is rejected

Nothing is posted anywhere. You choose where to paste the link or summary.

How to explain this in an interview

"For an age field that accepts 18 to 60, I first split inputs into partitions: below 18, 18 to 60, above 60, plus invalid formats like blank, text and decimals. I test one value from each. Then I add boundary values; with 3-value analysis that is 17, 18, 19 and 59, 60, 61. If the developer wrote age < 60 instead of age <= 60, only 60 fails, which is exactly why boundaries matter."

Next recommended topicDefect Life Cycle

Progress is saved on this browser only. It is not linked to your account and other devices will not see it.