> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/running-tests.md).

# Running tests

- [Running locally](https://docs.drizz.dev/running-tests/running-locally.md): Run a test on the device connected to your Mac, watch each step execute, and stop the run.
- [Test plans](https://docs.drizz.dev/running-tests/test-plans.md): A test plan is a set of tests plus how to run them — devices, app build, dataset, concurrency and a quality gate.
- [Creating & Running a plan](https://docs.drizz.dev/running-tests/creating-and-running-a-plan.md): Create a test plan, add tests, pick devices and data, set concurrency and a quality gate, run it, and read the run screen.
- [Devices](https://docs.drizz.dev/running-tests/devices.md): The three places a Drizz test runs — your Mac, the Drizz device cloud, or your org's private devices — and what happens when none is free.
- [Self-healing](https://docs.drizz.dev/running-tests/self-healing.md): When a step fails, Drizz repairs it mid-run instead of failing the whole test. Healed steps are badged in the report.
- [Caching](https://docs.drizz.dev/running-tests/caching.md): Drizz reuses how it resolved a step on a screen it has seen before. Cached steps run faster and cost less.
- [Game mode](https://docs.drizz.dev/running-tests/game-mode.md): Games don't expose a normal view hierarchy, so Drizz can run vision-only. Game mode is enabled per app by Drizz.