If there’s one place where defects love to hide, it’s at the edges.

Boundaries are where systems often fail:

• Off-by-one errors
• Incorrect comparisons
• Missing conditions

That’s why Boundary Value Analysis (BVA) is one of the most powerful test design techniques in software testing.

It builds directly on Equivalence Partitioning and focuses on the most error-prone areas: the boundaries between partitions.

---

What Is Boundary Value Analysis?

Boundary Value Analysis is a black-box testing technique that focuses on testing values at the edges of input ranges.

Instead of testing just any value in a range, BVA targets:

• Minimum values
• Maximum values
• Values just below and just above boundaries

Key idea:

👉 Defects are more likely to occur at boundaries than in the middle of ranges

---

Why Boundaries Are Risky

Developers often make mistakes when implementing conditions like:

• ≥ vs >
• ≤ vs <
• Incorrect limits
• Missing edge checks

These lead to classic bugs such as:

• Accepting invalid values
• Rejecting valid values
• Crashes at extreme inputs

BVA is designed to catch these issues.

---

Basic Example

Requirement:
“The system accepts values between 1 and 100.”

Boundaries:

• Lower boundary: 1
• Upper boundary: 100

Test cases using BVA:

• 0 (just below lower boundary)
• 1 (on lower boundary)
• 2 (just above lower boundary)
• 99 (just below upper boundary)
• 100 (on upper boundary)
• 101 (just above upper boundary)

These 6 tests provide strong coverage.

---

Comparing with Equivalence Partitioning

Equivalence Partitioning:

• Focuses on groups of values
• Tests one value per partition

Boundary Value Analysis:

• Focuses on edges of those groups
• Tests values around boundaries

👉 EP reduces test cases
👉 BVA increases defect detection at critical points

Together, they are very powerful.

---

Types of Boundaries

BVA can be applied to different types of data:

1️⃣ Numeric Ranges

Most common use case.

Example:
Age between 18 and 65.

---

2️⃣ String Length

Example:
Password must be 8–16 characters.

Boundaries:

• 7, 8, 9
• 15, 16, 17

---

3️⃣ Lists and Collections

Example:
Maximum 10 items in a cart.

Boundaries:

• 9, 10, 11

---

4️⃣ Dates and Time

Example:
Booking allowed between specific dates.

Test boundaries around:

• Start date
• End date

---

Two Approaches in BVA

1️⃣ 2-Value BVA (Minimum approach)

Test only boundary values:

• Min
• Max

2️⃣ 3-Value BVA (Standard approach)

Test:

• Boundary
• Just below
• Just above

ISTQB typically expects the 3-value approach.

---

Practical Example

Requirement:
“Password length must be between 8 and 16 characters.”

Test cases:

• 7 (invalid)
• 8 (valid)
• 9 (valid)
• 15 (valid)
• 16 (valid)
• 17 (invalid)

This ensures edge coverage.

---

Common Mistakes

❌ Testing only boundary values (ignoring just below/above)
❌ Not identifying all boundaries
❌ Confusing partitions with boundaries
❌ Ignoring invalid edge cases

Good testers always test both sides of boundaries.

---

When to Use Boundary Value Analysis

BVA is ideal when:

• Input ranges are defined
• Limits exist
• Edge cases are critical

Common scenarios:

• Form validations
• Business rules
• System limits
• API constraints

---

ISTQB Exam Perspective

For ISTQB Foundation Level, remember:

• BVA focuses on boundaries
• Test values: below, at, and above boundaries
• Often combined with Equivalence Partitioning
• Detects edge-case defects

Expect questions asking you to identify correct boundary test cases.

---

Final Thoughts

Most defects don’t hide in the middle.

They hide at the edges.

Boundary Value Analysis helps testers focus on these critical points and detect issues early.

Combined with Equivalence Partitioning, it creates a strong foundation for effective test design.

Test smart. Test the edges.