Boundary, Calculation, and State Errors: The Defect Classes QA Should Hunt

Many defects come from predictable classes of error. Boundaries, calculations, and state transitions are three of the most important because they appear across almost every software domain.

A professional tester uses these classes as prompts for better test design.

Boundary errors

Boundary errors happen near limits: minimum values, maximum values, dates, lengths, thresholds, permissions, quantities, and capacity limits. If a system allows 1 to 100 items, the interesting tests are often 0, 1, 2, 99, 100, and 101.

Boundaries are powerful because developers and requirements often describe the normal range more clearly than the edges.

Calculation errors

Calculation errors include rounding, currency precision, tax rules, discounts, time zones, unit conversion, ranking, aggregation, and statistical formulas. These defects can be costly because results may look plausible while still being wrong.

Good calculation tests include simple known examples, edge values, negative cases, and reconciliation against trusted sources.

State errors

State errors happen when the system forgets, confuses, or mismanages where a user, record, transaction, or process is in its lifecycle. Draft, submitted, approved, cancelled, expired, paid, refunded, and failed states all need clear rules.

The best QA teams build test ideas around these defect classes because they repeatedly expose real production risk.

How to use this as a working habit

The practical value of this topic is in daily test design. Use it when reviewing a requirement, creating examples, selecting data, choosing boundaries, or explaining why a particular test matters.

Fundamentals are not junior concepts. Senior testers use them with more judgment: less ceremony where risk is low, more discipline where ambiguity, impact, or repeatability matter.

A useful habit is to ask what decision this concept supports. If the answer is unclear, the testing activity may need refinement. Good fundamentals should make the work sharper: clearer scope, better examples, stronger evidence, and more honest communication about what remains unknown.