Success Toast Lingers After Failed Retry
Med.ToastsLocators
Mission
- Incident
Transient notification UI is a common false-positive source because old success banners can outlive the state they describe
- Goal
Trigger the live action, avoid stale toast assumptions, and prove the current run reaches done
- Pass condition
Trigger the current run action
What counts
- Trigger the current run action
- done lifecycle for the active run
- current toast reports saved state for the current run
Constraints1 rules + 1 mutation note
Rules
- Do not use stale toast messages from previous runs as success evidence
Mutation
- Toast stack ordering can preserve stale success above active run events
Hint 1
Action: Trigger the current run action.
Hint 2
Assertion: Assert done lifecycle for the active run.
Hint 3
Assertion: Assert current toast reports saved state for the current run.