Interactions Reference

Tap

Touch a screen element you describe in plain language. Tap one to ten times, repeat until a condition holds, AI element search, region narrowing, and Position Memory caching for speed.

Tap is the single most-used interaction. You describe the element you want to touch; Mavster finds it on screen and taps it. Position Memory makes repeated taps of the same element fast and cheap.

Quoting exact text

Wrap any text that should be matched exactly in quotes. Mavster will then match that literal text instead of interpreting the description loosely. Single quotes ('Sign In'), double quotes ("Sign In"), backticks, and curly quotes from auto-correct all work.

Without quotes	With quotes
`Tap the sign in button`	`Tap the 'Sign In' button`
`Tap the email field`	`Tap the 'Email' field`

Use quotes when the exact label matters; skip them when the description is shape/role/position-based ("the X icon in the top-right corner", "the second card in the list").

Settings

The Tap editor exposes:

Field	What it does
Control description*	Plain-language description of the element to tap. Supports $placeholders.
Repeat until condition	Optional. Leave blank for a normal tap. When set, Mavster taps over and over until this yes/no condition becomes true — the stepper pattern, e.g. 'the value is at least 200'. Each round fires Tap Count taps.
Region of Interest	Default 'all'. Narrows the search to a band of the screen (top nav, content, bottom nav, etc.) for better accuracy and lower cost. See Region of Interest.
Tap Count	1 to 10. Default 1. Set to 2 for a double-tap, or higher to fire several taps in a row. Also the number of taps per round when Repeat until is set.
AI Segmentation	How the AI looks at the screen. Choose None, Auto, or Force Fresh. See AI Segmentation modes.
Position Memory	On by default. With Position Memory on, Mavster validates and reuses a remembered tap position before falling back to a fresh resolution. A 'Clear' button appears once memory has been stored for this step.

When the test's self-healing mode is Per Step, a per-step Self-healing toggle also appears.

Edit Tap Interaction modal showing Control description 'the Sign In button', an empty Repeat until condition field, Region of Interest, Tap Count 1, AI Segmentation picker, and Position Memory toggle on.

Repeat until a condition

Leave Repeat until condition blank and Tap is a single touch. Fill it in and Tap becomes a loop: Mavster checks the condition, and while the answer is still no it taps and checks again — stopping the moment it's yes. This is the stepper pattern: tap the '+' until the quantity reaches 10.

Mavster checks before the first tap, so a condition that's already satisfied taps zero times.
Each round fires Tap Count taps, then lets the screen settle before re-checking. Raise Tap Count when the target needs many presses to get there.
It never loops forever. Mavster stops and fails the step if the value stops changing (the control is maxed out or stuck), or after a built-in maximum number of rounds. A failed loop is self-healing-eligible like any other step.

Phrase the condition as a plain yes/no check, the same way you would a Visual Assert. Each check is an AI look at the screen, so a long loop costs more credits than a single tap — see Credits.

What's possible

Tapping a labeled element: the 'Sign In' button, the 'Email' field (quoted text matches exactly).
Tapping by visual description: the second item in the list, the X icon in the top-right corner.
Multiple taps: set Tap Count up to 10 — e.g. 2 for a double-tap.
Repeat-tap a stepper: set Repeat until condition to the quantity is at least 10 and Mavster taps until it's there.
Region narrowing for accuracy and speed: a Tap restricted to the bottom navigation won't be confused by a same-named element in the body.
Parameter-driven taps: tap on the row labeled '$product'.

What's not possible

More than ten taps in one fixed step — Tap Count maxes at 10. For an open-ended count use a Repeat until condition; for more than ten guaranteed taps, chain Tap steps.
Long-press / press-and-hold gestures — Tap is a discrete touch. Use Drag for sustained input.
Tapping at an absolute coordinate — Tap always resolves the target by description (or remembered position). For coordinate-based input, use Drag in hardcoded mode.
Tapping offscreen elements — scroll the target into view first with Scroll using its "until" condition.

Common patterns

Pair with Visual Assert. A common mini-pattern: Visual Assert (assert the screen) → Tap (a button on it) → Visual Assert (assert the next screen).
Use a region for tab bars and nav. Tabs and navigation icons are the highest-payoff targets for narrowing the region — narrowing the search avoids surprises when a same-name element appears in the page body.
Leave Position Memory on by default. Mavster validates the remembered spot before reusing it; the cost is tiny and the speed-up is real.
Prefer Repeat until on steppers. For quantity pickers and +/− controls, a Repeat until condition is more robust than a fixed Tap Count — it stops exactly when the value is right, whatever the starting point.

Region of Interest — when and what to pick.
Position Memory — how the memory toggle works in detail.
AI Segmentation modes — when to use None, Auto, or Force Fresh.