Rehearse a disrupted commute with fixed feed data
Most checks cover a clean daytime trip. Before the pilot, rehearse a saved late-night commute through feed outage, cancellation correction, and app restart.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Scenario testing · Release readiness · Operational handoff
Estimated field mix
- Quality engineering60%
- Mobile40%
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 Northline commuter app plans bus and rail trips from synthetic timetable and alert feeds. Riders save journeys and choose optional reminders. The scope excludes ticket purchases, safety guarantees, and continuous location collection.
Setup prerequisites
- Synthetic timetable with explicit time zones and service dates
- Departure, alert, and permission adapters with failure fixtures
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- TRIP-102 · Keep the last train on the correct service day
- TRIP-104 · Label stale departures when the live feed stops responding
- TRIP-105 · Apply cancellation updates to the right departure instance
- TRIP-106 · Stop refreshing a journey after the rider leaves it
- TRIP-107 · Make departure reminders honest about permission and schedule changes
- TRIP-101 · Give saved journeys names that survive station renames
- TRIP-108 · Recover a route search when the timetable changes mid-session
- TRIP-103 · Explain transfers without relying on line colors
- TRIP-109 · Offer nearby stops without making location mandatory
Acceptance criteria
- A deterministic scenario records which timetable revision, departure identity, and freshness label appear at each step.
- Restart preserves the saved journey without restoring an obsolete reminder.
- The handoff states fixture coverage and unresolved live-feed assumptions explicitly.
Implementation constraints
- Use a controllable clock and adapters; do not depend on actual transit services or notification delivery.
Verification to include
- Run the rehearsal twice and compare the ordered visible states.
- Inject an invalid feed timestamp and an interrupted dataset update; no current-live label or mixed-version trip appears.
Deliverables
- Disruption rehearsal script and pilot support checklist
Rollout and recovery
Require the fixed-data rehearsal before app updates; pause pilot expansion on misleading freshness or reminder state.
Value of the work
For the engineer: Practice temporal modeling, feed reconciliation, battery-conscious refresh, and mobile permission design.
For the team: Review how an engineer communicates uncertainty and keeps a consumer app useful under unreliable data.
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.