> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/no-code-studio/reference/keyword-reference.md). # Keyword reference Around 50 keywords are available. These are the ones you will actually use. Open the full catalogue any time with **right-click → All Commands**. ## Element actions | Keyword | What it does | Key parameters | | ------------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------- | | Press Element | Taps the element | element, repeat (1), index (0), offset x/y (0) | | Enter Text | Taps the element, then types into it | element, text | | Enter Text Direct | Types into whatever already has focus. No element, no tap | text | | Enter Text Using Keyboard | Types key by key through the device keyboard, for fields that ignore programmatic input | text | | Enter Number | Types a numeric value | number | | Clear Element Text | Empties a text field | element | | Get Text | Reads the element's text into a variable | element, variable name | | Press By Coordinates | Taps an absolute point | x, y (device pixels), repeat | | Press By Percentage | Taps a relative point. `50, 50` is the centre of the screen | x, y (0-100), repeat | | Press Keycode | Sends an Android key code: 4 is Back, 3 is Home, 66 is Enter | keycode | | Detect And Press | Taps the element if it appears within the timeout. Passes even if it never appears | element, timeout | | Select Dropdown Option | Scrolls a dropdown looking for an option and picks it | option, timeout | ## Scrolling and swiping | Keyword | What it does | Notes | | ---------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------ | | Scroll | Scrolls from an element | Up and down only. Use Swipe for sideways movement | | Scroll Until Element Appears | Keeps scrolling until the element shows up or the timeout expires | Up and down only | | Swipe | Swipes from an absolute starting point | start x, start y, direction, distance in device pixels | | Swipe By Percentage | Same, but the distance is a percentage of screen height (up/down) or width (left/right) | Not pixels: this one is the exception | | Swipe Until Element Appears | Keeps swiping until the element shows up | All four directions | ## Validation | Keyword | What it does | | ----------------- | ------------------------------------------------------------------------------- | | Assert Presence | Checks the element exists in the UI tree. Accepts a list and a rule (any / all) | | Assert Visibility | Same fields, but checks the element is actually rendered on screen | | Validate Element | Checks a state of the element: visible / invisible, enabled / disabled | | Validate Screen | Checks the screen as a whole | {% hint style="warning" %} **Presence is not visibility.** Assert Presence passes for an element that exists in the UI tree but has been scrolled out of view. When you mean "the user can see this right now", use Assert Visibility. On Validate Element, **visible / invisible** check the screen, so they work for image and OCR matches. **enabled / disabled** need a real element handle and do not work on image or OCR matches. {% endhint %} ## App actions | Keyword | What it does | | ---------------- | ----------------------------------- | | Launch Other App | Opens a different app on the device | | Terminate App | Closes an app | | Background App | Sends the app to the background | ## Device actions Rotate Device, Set Orientation, Lock Device, Unlock Device, Shake Device. ## Waits and inspection | Keyword | What it does | | ------------------- | -------------------------------------------------------------------------------- | | Sleep | Pauses for a number of seconds. Use sparingly; prefer a wait-for-element keyword | | Capture Screenshot | Takes a screenshot into the report at this point | | Capture Page Source | Dumps the UI tree into the report | ## Keywords you will not see A few keywords are not in the picker because App Studio handles them for you: * **App launch** is generated from the app you pick on the run screen. * **Branching** is authored through the [Condition](https://docs.mozark.ai/no-code-studio/authoring-tests/conditions) block rather than a keyword. ## Search-area parameters Most element keywords carry four extra parameters, **Search area X, Y, width, height**, all percentages of the screen, defaulting to `0, 0, 100, 100`. See [Recording tests](https://docs.mozark.ai/no-code-studio/authoring-tests/recording-tests). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mozark.ai/no-code-studio/reference/keyword-reference.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.