LEARN. PRACTICE. GROW.Concept and mechanism
Anticipating testing starts by improving understanding of the need. In an Example Mapping conversation, distinguish the rule, examples illustrating it, and unanswered questions. An unknown outcome should not become an assertion merely because a developer has already implemented one option. In a fictional portal, the rule says requests above 750 euros require a second authorization. Values of 749.99, 750, and 750.01 help expose the boundary, but currency, precision, and rounding also need confirmation. The 750 example belongs to the not-above rule; if the actual policy is unclear, request an owner decision before automating the expectation.
Guided application
Split an export story by usable outcomes: first one format for a defined population, including validation, authorization, and consumer readability. Delivering only the database table does not demonstrate that outcome. Keep deferred exceptions explicit and do not remove a mandatory control to fit the iteration. A storyboard can expose what users see when their session expires; a list of test conditions can add what should happen to an already submitted request. Ask someone to seek an example contradicting the initial interpretation. This review reduces the risk that the team chooses only data confirming its preferred solution.
Above 750 excludes exactly 750 under the stated fictional rule.
Common pitfalls
Current behavior treated as a rule; splitting only by layer; confirmation-only examples.
Related topics: Strategy, risk, and regression · Team, feedback, and specialists · Planning, metrics, and improvement
Write examples that make the decision observable.
Reference: Introducing Example Mapping · CTAL-AT v2.0 (2026)