Check the request-return-resubmit journey before release
Form tests passed, but the last release lost a quote when finance returned a request. Add a deterministic journey through return, edit, and resubmission.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- End-to-end testing · Release engineering · Recovery
Estimated field mix
- Quality engineering70%
- Frontend30%
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
The fictional Beacon operations team buys equipment through a browser form. Finance checks totals, departments, and quotes. Scope is one currency per request and an approval API contract; payments and accounting integration are excluded.
Setup prerequisites
- Synthetic department and cost-center directory
- Draft, submission, and approval API fixtures
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- FORM-102 · Make the total match the submitted line items
- FORM-101 · Point requesters to the field that needs fixing
- FORM-103 · Clear an orphaned cost center when department changes
- FORM-104 · Save drafts without overwriting a second browser tab
- FORM-105 · Show attachment quarantine and upload recovery clearly
- FORM-107 · Close the duplicate-submit gap after a slow response
- FORM-106 · Show finance what changed since their last review
- FORM-108 · Retire approval controls when authority changes
- FORM-109 · Make a 40-line request usable on a narrow screen
Acceptance criteria
- The journey covers submission, finance return, changed amount, and review of the new revision.
- Attachment and request identities stay stable across revision creation.
- Resubmission failure leaves the earlier revision readable and the new draft recoverable.
Implementation constraints
- Synthetic users and API fixtures establish workflow behavior, not live-service readiness.
Verification to include
- Run twice from clean fixtures and compare final revision relationships.
- Fail after draft save before submission acknowledgement; attachments survive and requests do not duplicate.
Deliverables
- Workflow browser check and release/rollback checklist
Rollout and recovery
Gate form releases on this journey; stop rollout on identity loss and restore the prior form build.
Value of the work
For the engineer: Practice form modeling, exact totals, revision handling, and collaboration under failure.
For the team: Inspect whether a developer protects business workflows from duplicate, lost, or misleading submissions.
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.