What You Configure
Before starting a run, you select:- Scenario — Which test plan to execute
- Build — Which version of your game to test (APK, IPA, or web URL)
- Device — Which device to run on (model, platform)
- Skills — Which behavioral instructions to give the agent for this run
- Knowledge — Auto-selected based on the build version (always included)
Run Lifecycle
Every run moves through a clear sequence of stages:1. Pending
The run has been created but hasn’t started yet.2. Device Preparing
A remote device is being provisioned and set up. This includes:- Installing support services on the device
- Installing your game build
- Launching the app
- Confirming the video stream is working
3. Agent Running
The AI agent is actively playing your game, working through checkpoints. During this stage you can:- Watch live — See the device screen in real time
- Track progress — See which checkpoints have been reached, are in progress, or are pending
- View agent reasoning — See the agent’s thought process as it decides what to do next
4. Completed
The run has finished. The final status depends on checkpoint results:- Passed — All required checkpoints were completed successfully
- Failed — One or more required checkpoints failed
Pass/Fail Logic
The rule is simple: all checkpoints must pass for the run to pass.- If any checkpoint fails (timeout, skip, or agent failure), the run stops and is marked as failed
- The run result gives you a clear breakdown: how many checkpoints passed, failed, or were skipped
Watching a Run in Progress
While the agent is running, you get real-time visibility into:- Live video — The device screen, streamed to your browser
- Checkpoint progress — A checklist showing which milestones have been reached
- Agent reasoning — The agent’s thought process for each action it takes
- Action log — Every tap, swipe, and interaction the agent performs
Interactive Device Control
The device screen isn’t just a video feed — it’s fully interactive. You can click, drag, swipe, and type on the device directly from your browser. If you see the agent is stuck on a certain screen, you can step in and navigate it to where it needs to be. The agent will pick up from there and continue on its own.Run Artifacts
After a run completes, several artifacts are saved for review:| Artifact | What it contains |
|---|---|
| Video recording | Full recording of the device screen throughout the run |
| Device logs | System and app logs captured from the device |
| Agent reasoning | The agent’s decision-making process — what it saw, what it considered, what it chose to do |
| Action log | Every interaction the agent performed (taps, swipes, text input), with timestamps |
| Checkpoint screenshots | A screenshot captured at the moment each checkpoint was reached or failed |
Playground Mode vs Formal Runs
Duzz offers two ways to run a scenario:| Formal Run | Playground Mode | |
|---|---|---|
| Purpose | Structured testing with recorded results | Interactive exploration and debugging |
| When agent finishes | Run ends, device shuts down automatically | Agent pauses at the last checkpoint — device stays alive for you to interact with |
| Device behavior | Released immediately after the run | Stays available until you close it (30-minute idle timeout) |
| Checkpoints | Locked — uses the scenario’s checkpoints as-is | Editable — you can add, remove, and reorder checkpoints before and during the session |
| Best for | Regression testing, CI pipelines, formal QA passes | Iterating on scenarios, debugging failures, exploring the game |
Cancelling and Re-running
- Cancel — Stop a run that’s in progress. The device is released and partial results are saved
- Re-run — Start a new run with the same configuration. Useful after fixing a build or tweaking a scenario
Timeouts
- Checkpoint timeout — Each checkpoint has its own timeout (default 5 minutes). If the agent can’t reach the goal in time, that checkpoint fails
- Global timeout — Runs have an overall time limit of 1.5 hours. This prevents runaway sessions from consuming resources indefinitely
- Pause timeout — In playground mode, if you don’t interact with the paused device for 30 minutes, it shuts down automatically
Quick Reference
| Concept | What it is |
|---|---|
| Run | One execution of a scenario on a build + device |
| Build | A specific version of your game (APK, IPA, or URL) |
| Device | The mobile device or browser the agent plays on |
| Playground | Interactive mode — agent pauses when done, device stays alive |
| Formal Run | Structured mode — run ends cleanly, device released |
| Artifacts | Video, logs, screenshots, and reasoning saved after a run |