Assert / Verify
The check. It looks for one thing and sends the run down `true` or `false` depending on what it found.
Assert element/text exists → branch
Reach for it when
- The actual point of the test — the confirmation screen, the error banner, the item in the cart.
- Guarding a branch: take one path when the user is already logged in, another when they are not.
Every setting this block has. A field marked only when appears once you have chosen the mode above it — those are alternatives to each other, not extra things to fill in.
- Selector / textRequiredstarts at —
text / id / xpath — pick it visually from an upstream Dump UI below.
only when Pick the element on the device when it runs = off
- Assert thatstarts at The element exists
Passes (→ true branch) when the element matches this; otherwise the run takes the false branch.
The element existsThe element does NOT exist - Pick the element on the device when it runsstarts at off
Pause the run and stream the live device: tap the element to check on the live screen, then it verifies existence and branches true/false (1 min limit — the step is skipped if you don't pick in time). Disables scheduling.
Name what has to be there
Same selector language as Tap: visible text, a resource id, or an xpath.
Assert / VerifySettings Selector / texttext / id / xpathOrder confirmedAssert thatThe element existsDecide which way round passing is
“Does NOT exist” is a real assertion, not a workaround — an error banner being absent is the thing you want to prove.
found → true Connect both sides
`true` is the side where the check held. Leaving `false` unconnected does not fail the run — it just ends there, quietly.
Assert / VerifyIdletruefalse
- `true` when the check held, `false` when it did not — and the number of elements that matched, on both.
- A false branch is not a failure. If a failed check should mark the run red, put Fail the Run on that side.
- Assert on a screen that has not finished drawing fails for the wrong reason. Put a Wait for Element in front of it.