Base120 · Inversion

Boundary Testing

IN · Inversion

Explore extreme conditions to find system limits and breaking points

Model code
IN7
Transformation
IN (Inversion) — Improve by removing, reversing, or stress-testing assumptions.
Priority
7 of 20
Framework
HUMMBL Base120 — 120 mental models across 6 transformations

When to use

"Use to find system limits before they find you. Explore extreme conditions — zero load, maximum load, empty inputs, malformed inputs, simultaneous failure of multiple components. Boundaries reveal assumptions that normal operation hides."

Example

"A payment system works for all test transactions. Boundary testing — what happens with $0.00, $0.01, $999,999,999.99, negative amounts, 17 decimal places? The system crashes on negative amounts because the validation assumed positive inputs."

Common misuse

"Testing only the boundaries you can imagine. Real-world failures often occur at boundaries no one thought to test. Pair boundary testing with red teaming (IN10) for adversarial boundary discovery."

Also known as

Edge Case TestingStress Testing

Related models