Switch an active Fishing Program after a safe test incident and verify that every downstream view uses the new current Beat.
Before you start
- Act as
- The guide assigned to the active Fishing Program
- Starting state
- The Program is approved and in progress, with no submitted Fishing Report
- Test data
- At least one other active Beat belongs to the same lodge
Run the scenario
- 1GuideTrailhead Mobile · Program timeline
After starting the Program, select Change Beat due to incident.
Expected evidence
The flow opens with a searchable list of active same-lodge Beats and no oversized current-Beat card.
- 2GuideTrailhead Mobile · Change Beat
Select a different Beat, continue, choose Access closed, and add a short test note.
Expected evidence
The motive is collected after Beat selection, where the Beat list cannot cover it.
- 3GuideTrailhead Mobile · Review Beat change
Verify the current-to-new move, motive, note, and listed effects, then confirm once.
Expected evidence
The Program immediately shows the new current Beat, preserves the planned Beat, records a localized timeline message, and requires no Operations approval.
- 4GuideTrailhead Mobile · Fishing Report
Open the linked report and submit an accurate test outcome, with or without catches and photos.
Expected evidence
The report shows the Program's current Beat without an independent picker; submitted evidence cannot contradict the Program Beat.
Scenario completed
The Program, timeline, draft report, and Operations view share one current Beat
- Current Program Beat
- Previous effective Beat→Selected same-lodge Beat
- Linked draft Fishing Report
- Previous effective Beat→Current Program Beat
If it does not match
- A submitted Fishing Report locks further Beat changes; correct the report through the supported correction flow instead of changing the Program behind submitted evidence.
- If the target Beat is inactive, belongs to another lodge, or current Program data changed, refresh and choose a currently eligible Beat instead of forcing the mutation.