QA Engineers Replacing Manual Click-Testing
Replay every UI flow on every PR. Stop click-testing the same five screens by hand.
The setup
QA engineers spend most of their time clicking through the same UI flows. CodeLoop's `codeloop_record_interaction` captures a flow once; `codeloop_interaction_replay` runs it on every verify cycle, asserting the outcome. Combine with video capture and you have an evidence trail that survives any 'did you actually test this?' challenge.
Workflow
- Record flows once. codeloop_record_interaction captures click / type / hover sequences with screenshots at each step.
- Replay on every verify. codeloop_interaction_replay runs every recorded flow and asserts the captured outcomes.
- Video evidence. codeloop_start_recording / codeloop_stop_recording produce a screen recording for every replay run.
- Cross-platform. Works on macOS, Windows, Linux, Android (adb), iOS (simctl) — same recorded flow runs on every target.
- Gate the PR. codeloop_gate_check requires every recorded flow to pass before returning ready_for_review.
FAQ
Do I need to learn a DSL for the flows?
No. codeloop_record_interaction captures real clicks + keystrokes; you confirm the captured steps and CodeLoop generates the JSON spec. No code required.
Can flows survive UI redesigns?
Mostly yes. CodeLoop uses accessibility-tree selectors first (resilient to visual change), with a pixel-coordinate fallback for non-accessible widgets. After a major redesign, codeloop_record_interaction re-records the flow in <30s.
Does this work with mobile apps?
Yes. Android via adb, iOS via simctl, plus react-native + Flutter via the standard widget tree. Maestro YAML can also be ingested if you already have flows there.