Interactions Reference

Wait Until

Poll the screen for up to N seconds and continue as soon as a visual condition is met. The robust alternative to Wait.

Wait Until polls the screen and continues the test as soon as your Until condition is satisfied — or fails the step if Max Wait elapses first. Almost always preferable to a fixed Wait for "wait for X to load" gates.

What it does

Mavster polls the screen and checks whether Until is satisfied. As soon as it is, the step succeeds and the next step starts. If Max Wait elapses without the condition being met, the step fails.

Phrase the Until field as a question, the same way you would for Visual Assert — Mavster will keep polling and stop the moment the answer is yes.

Settings

The Wait Until editor exposes:

Field	What it does
Max Wait (seconds)*	Maximum time to wait before failing the step.
Until	The visual condition to wait for. Placeholder: 'e.g., You see a checkmark next to the submit label'.

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

Edit Wait Until Interaction modal with Max Wait (seconds) 10 and Until 'Do you see the home feed?'.

What's possible

Wait for a specific screen to appear: Until = Is the home tab selected and the feed loaded?
Wait for a long-running task to finish: Until = Has the upload progress bar reached 100%? with Max Wait = 60.
Wait for a transient state: Until = Do you see the 'Saved' toast?

What's not possible

Wait for the absence of something reliably — Mavster is better at confirming presence than absence. Phrase the condition as a positive state of the next screen ("Do you see the home feed?") rather than the disappearance of the previous one.
Wait conditioned on backend events — Mavster only sees the screen. If the only signal is a network response, you'll need a frontend hint (toast, loading spinner that disappears, etc.) for Wait Until to gate on.

Wait vs. Wait Until

Need	Use
Pause for a known fixed duration that doesn't depend on the app	Wait
Wait for a screen to be ready, a state to appear, an animation to settle	Wait Until
Pad around something flaky	Probably neither — fix the gate with a Visual Assert instead

Common patterns

Replace post-tap pauses. Instead of Tap → Wait (1.5 s) → Visual Assert (next screen), use Tap → Wait Until (next screen) → continue. Faster on the happy path, more robust under load.
Keep Max Wait honest. Use the longest realistic time, not 5 minutes "just in case". Long timeouts hide real regressions.
Until tends to mirror Visual Assert questions. That's fine — Wait Until is essentially a polling Visual Assert with a timeout.