Loading content
Boundary Value Analysis is a testing technique focusing on boundaries and edge ranges to detect defects at input limits. It is applied in unit, integration, and system tests and efficiently reduces the number of test cases by selecting critical values. This method reliably uncovers common off-by-one and range-handling faults.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Boundary Value Analysis is a testing technique that selects input and output values at the edges of ordered ranges to find defects where behavior changes.
In software test practice, Boundary Value Analysis emerged as a complement to equivalence partitioning: instead of choosing values randomly from a range, testers probe the edges of ordered input or output ranges directly. Test literature describes it as a technique for minimum, maximum, and transition values, because comparison and range-handling defects often appear there.
Think of each value range as a fence with posts. First define the relevant classes, then mark each boundary and test three points: just below it, exactly on it, and just above it. If the system behaves differently at the edge than expected, that short three-step check reveals where the transition logic is wrong.
The method evaluates observable behavior rather than internal implementation.
Values with similar expected behavior are grouped so not every individual value must be checked separately.
A boundary value sits at the edge of a range where behavior may change.
Values directly below and above the boundary show the transition between two ranges.
These defects often come from wrong comparison operators, count limits, or inclusivity at range edges.
The method is especially useful for numeric fields, lengths, quantities, date limits, and validation rules with a minimum or maximum. It reduces test effort, but it does not replace checks for state logic, combinations, or complex business rules. Its value depends on clearly defined business boundaries; otherwise you may test at the edge without testing the right edge.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.