tap
Dispatches a tap at specified x and y coordinates on a mobile device. Use for direct screen interaction during testing.
Instructions
Purpose: Dispatch a tap at specific screen coordinates.
Inputs:
x, y coordinates
platform (optional)
deviceId (optional)
Output Structure:
action_id, timestamp (ISO 8601), action_type
lifecycle_state: post-dispatch lifecycle state (pending_verification or failed)
source_module: runtime source of the action envelope
target.selector = { x, y }
success = true when the tap was dispatched
failure_code/retryable when dispatch fails
ui_fingerprint_before/ui_fingerprint_after when available
Recommended Usage:
Resolve coordinates deterministically
Call tap
If needed, wait for transition using wait_for_*
Verify with expect_screen or expect_element_visible depending on the intended outcome
Verification Guidance:
Prefer tap_element over tap when an element can be resolved
Follow RESOLVE → ACT → WAIT (if needed) → EXPECT
Use expect_screen for navigation and expect_element_visible for local UI changes
Do not use wait_for_* alone as final verification when an applicable expect_* tool exists
Failure Handling:
TIMEOUT → retry once
UNKNOWN → capture a snapshot and stop
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| x | Yes | X coordinate | |
| y | Yes | Y coordinate | |
| deviceId | No | Device Serial/UDID. Defaults to connected/booted device. | |
| platform | No | Platform to tap on |