Create boundary partitions for delivery eligibility
Only ordinary postal codes are tested, while minimum basket size and service boundaries determine eligibility.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Boundary testing · Test design
Estimated field mix
- Quality engineering100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional retailer is changing delivery options. Its regression suite is large, but no one can explain whether inventory, totals, or recovery behavior is covered.
Setup prerequisites
- Build a minimal local checkout fixture with synthetic prices, inventory, and a mock delivery provider.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Partition valid, excluded, and malformed destinations.
- Cover basket thresholds below, at, and above the boundary.
- State the expected reason when no option is eligible.
Implementation constraints
- Use fictional destinations and rates.
Verification to include
- Exercise representative values from every partition.
- Reject malformed input without calling the mock provider.
Deliverables
- Eligibility case table.
Rollout and recovery
Version the case table with the delivery rules.
Value of the work
For the engineer: Practice risk analysis, exploratory testing, and evidence-based release decisions.
For the team: Provide a reviewable release assessment tied to customer-impacting invariants.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.