Appvecta Replay
Reproduce it on demand, not on a good day.
A failure is only useful if you can make it happen again. Replay re-runs the exact stored flow against a declared initial state, and is honest when it cannot.
The declared initial state
- App-data reset
- Account and test data
- Network assumption
- Orientation and locale
- Required permissions
- Device awake and unlocked
If a precondition cannot be re-established, the replay is labelled best effort rather than silently run anyway.
The repair loop
Failure → a classified report with evidence → "Open related code" ranks source locations via an impact query → "Ask the Agent to investigate" builds context from the report, the failing step’s evidence and the Brain subgraph → the agent proposes a repair → you approve → rebuild → replay → the new report links back to the previous one.
All three approvals in that loop are explicit. None of them can be turned off.
Flaky is not passed
A step that only passes on retry is marked flaky, not passed, and appears in the summary as such. Flows themselves are authored YAML, committed with the project and reusable across similar codebases.