Software Testing · Lesson 5 of 8

Test design: boundaries, partitions and decision tables

Cover more with fewer tests using equivalence partitioning, boundary value analysis and decision tables.

You can't test every possible input. Test design techniques choose a small set of inputs that still catches most bugs.

Equivalence partitioning

Divide inputs into groups the system should treat the same way, then test one value from each group. If an age field accepts 18–60, the partitions are: below 18 (invalid), 18–60 (valid), above 60 (invalid).

Boundary value analysis (BVA)

Bugs cluster at the edges, often from < written instead of <=. Test the boundaries and values just around them: 17, 18, 19 and 59, 60, 61.

Decision tables

When the result depends on combinations of conditions, list each combination and its expected outcome. Every column becomes a test case.

State transition

For features with states (order: placed → packed → shipped → delivered / cancelled), test valid transitions and also invalid ones, such as cancelling after delivery.

Example

Practise on any app you use
Rule: free delivery if order ≥ ₹499 OR the user has a Plus membership. COD (cash on delivery) not allowed above ₹5,000.

Decision table: C1    C2    C3    C4 Order ≥ ₹499         Y     Y     N     N Plus member          Y     N     Y     N
  ---------------------------------------- Free delivery        Y     Y     Y     N

Boundary values for order amount: ₹498, ₹499, ₹500 ₹4,999, ₹5,000, ₹5,001 (COD check)

What to notice

• Four combinations → four test cases, none missed.
• Boundaries 498/499/500 catch a ">" vs ">=" mistake.
• The COD rule has its own boundaries — each rule gets its own BVA.

Apps, IDs and data are fictional examples written for practice.

Key points

  • Partition inputs into groups; test one per group.
  • Test at and around every boundary.
  • Use decision tables for combinations of conditions.
  • Test invalid state transitions too.

Quick check

A field accepts 1 to 100. Which set best applies boundary value analysis?

Practice task

A password must be 8–16 characters with at least one digit. Write the partitions and the boundary values you would test.

Interview corner

What is equivalence partitioning?

Grouping inputs that should behave the same so one value per group represents it — reducing test cases without losing coverage.

Why do bugs occur at boundaries?

Off-by-one mistakes in conditions and loops (< vs <=, starting at 0 vs 1) show up exactly at the edges of valid ranges.

Original lesson written by the InfoparkDaily team · © 2026 InfoparkDaily · Free to learn — no paid course or subscription.