> 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/writing-tests/command-index.md). # Command index Every command Drizz understands, in one table. A command that isn't here isn't a command — press `/` in the editor to confirm. ## Prerequisites * A connected device or emulator * An open test file ## Commands
CommandWhat it doesPage
# <text>A comment. The line is skippedThe shape of a test
Tap on <description>Tap an element described in plain EnglishTap
Type <text> in <field>Enter text into a field, focusing it for youType
Validate <condition>Assert something is true on screenValidate
Scroll <direction>Scroll by a fixed amount Scroll
Scroll <direction> by <n>%Scroll by a specific amountScroll
Scroll <direction> until "<target>" is visibleScroll until something comes into viewScroll
Swipe / Drag / SlideSynonyms of Scroll — same directional behaviorScroll
Wait Until <n> SecondsPause for a fixed timeWaits & timing
IF <condition> { … }Run steps only when the condition holdsConditionals
ELSE IF <condition> { … }Next branch when the IF doesn't matchConditionals
ELSE { … }Fallback branchConditionals
MAP_ACTION Tap on <description>Coordinate-based tap for unlabeled or canvas elementsMAP_ACTION
MAP_ACTION Drag <from> to <to>Drag a slider, seekbar, map pin or swipe-to-confirm controlMAP_ACTION
OPEN_APP <package>Launch an appSystem commands
KILL_APP <package>Force-stop an appSystem commands
CLEAR_APP <package>Wipe app data and reset to first launchSystem commands
MINIMISE_APP <package>Send the app to the backgroundSystem commands
PRESS_DEVICE_BACK_BUTTONAndroid hardware backSystem commands
SET_GPS(latitude=<lat>, longitude=<lon>)Mock the device locationSystem commands
ENABLE_WIFI / DISABLE_WIFITurn wifi on or offSystem commands
TOGGLE_LOCATIONToggle location servicesSystem commands
SET <var> = "<value>"Assign a variableStore & SET
SET <var> = screen(<description>)Capture structured data off the screenStore & SET
{{var}}Reference a variable in any commandWhich variable do I use?
{{var.field}}Reference one field of a structured variableWhich variable do I use?
CALL <module>Run a reusable moduleModules
CALL <module>(<param>={{value}})Run a module with parametersModules
PARAM <name>Declare a module parameter, inside the moduleModules
API:<api_name>Call a registered APIAPI steps
## Syntax conventions | Convention | Detail | | ------------------------------------------- | ---------------------------------------------------------------- | | **Angle brackets are placeholders** | `` means you type `com.shopease.android` | | **Keywords are case-insensitive** | `Validate`, `validate` and `VALIDATE` all work | | **System commands are written in capitals** | `OPEN_APP`, not `open_app` | | **Validation keywords** | `Validate`, `Verify`, `Confirm` and `Check` are the same command | | **Scroll conjunctions** | `until`, `till` and `untill` are all accepted after `Scroll` | | **Variables** | Anything in `{{ }}` is substituted before the step runs | ## Common mistakes | What you wrote | What happens | | --------------------------------- | ---------------------------------------------------------------------------------------------------------- | | `OPEN_APP` with no package name | Fails by design. The package argument is required | | `OPEN_APP:(com.shopease.android)` | Not supported. Use a space: `OPEN_APP com.shopease.android` | | `open_app com.shopease.android` | System commands are written in capitals — write `OPEN_APP` | | `Wait until the cart loads` | Accepted by the editor, but only fixed-duration waits are confirmed to wait. Write `Wait Until 10 Seconds` | ## Next * [The shape of a test](/writing-tests/writing-tests.md) — how the commands fit together * [Tap](/writing-tests/tap.md) — the most-used command * [Waits & timing](/writing-tests/waits-and-timing.md) — fixed waits and where they go *** *Last updated: 6 August 2026*