testmuai-appium-bindings

Appium runtime bindings for KaneAI v4 mobile exports.

Distribution name vs import name Install testmuai-appium-bindings; import testmu_appium.

Installation

pip install testmuai-appium-bindings

Quick start

A generated mobile test is a thin script over this runtime:

import testmu_appium
from testmu_appium import var, set_var

testmu_appium.configure(kane_run_v4=True, app_id="com.google.android.gm", platform="android")

@testmu_appium.test
def test(driver):
    with testmu_appium.step("Tap the Compose button"):
        testmu_appium.click(
            driver,
            selectors=[
                {"strategy": "view_id", "selector": "com.google.android.gm:id/compose",
                 "score": 90, "isXPath": False},
                {"strategy": "accessibility_id", "selector": "Compose",
                 "score": 80, "isXPath": False},
            ],
            description="PRIMARY: Compose button HINTS: bottom-right, red FAB",
            fallback_coordinates={"x_ratio": 0.8631, "y_ratio": 0.9012,
                                  "orientation": "portrait", "window": [1080, 2340]},
        )

if __name__ == "__main__":
    testmu_appium.run(test)

The generated code is platform-portable: it carries selector data and semantic key names only. Strategy compilation, keycode maps and picker machinery are runtime data tables keyed off the configured platform.

Configuration

configure() raises on unknown keys — a generator emitting a key this binding version does not understand fails at import instead of silently dropping it.

Screenshots

Perception screenshots come from the uiautomator2 server's MJPEG broadcaster where it is reachable, and from driver.get_screenshot_as_png() otherwise. The session asks Appium for the appium:mjpegServerPort forward on a local run target only — a cloud session's forward lives on the device host, which 127.0.0.1 here does not reach — and a stream that fails once is not tried again for the rest of the session. Perception.screenshot_source names the path that served the frame.

screenshot_source="mjpeg" takes the stream on any run target and forbids the Appium fallback; screenshot_source="appium" never opens the stream.

The generated call surface

The verb names and their parameters are a contract shared with the code generator, pinned on this side by tests/test_public_surface.py (BINDING_PUBLIC_SURFACE) and on the generator's side by its verb-table test. Both tables carry the same rows and are edited together.

Verbs come in three shapes:

• element — click, type, search, clear, select, scroll, scroll_until. Take selectors; run settle → find → act → heal.
• driver — drag, navigate, keyevent, app_lifecycle, device_control, wait, smartui_screenshot, check_until_condition, verify_assertion, textual_query, vision_query, network_query, network_capture_query. Take the driver, never take selectors, never heal.
• value — evaluate_math, math, execute_api, execute_db. Pure; take no driver at all.

verify_assertion(tree=...) and evaluate_math(tree=...) accept the recorded assertion_tree / mathmatic_tree the generator emits. assertion(...) and math(expression=...) are the flat-argument forms behind them and stay available for hand-written tests.

Network capture contracts

Generated artifacts should use network_capture_query(driver, contract=...) with network.capture.v1: exactly schema_version, a selector (method, url, zero-based occurrence, flow_id), and millisecond wait values. The provider is runtime configuration only: TESTMU_NETWORK_CAPTURE_URL selects the stable GET /v1/network/capture/flows, /flows/{id}, and /capabilities contract; TESTMU_NETWORK_CAPTURE_PROVIDER=lambda-har adapts a legacy /har provider. Without an explicit URL, a runtime that provides HOST_IP and PROXY_API_PORT derives the legacy endpoint (environment first, then rd-details.env in the temp directory), including authoring runs whose local run-target setting has not changed. network_capture_capabilities() reports provider readiness. network_query(...) remains a compatibility wrapper around the canonical contract.

evaluate_network_assertion(tree, contract_version="network.assert.v1") returns a deterministic passed/failed/indeterminate result with evidence and matching flow IDs. Failed or unavailable-body results raise NetworkAssertionError unless TESTMU_SKIP_ASSERTION_FAILURE is truthy.

Perception API

The UI-tree parser is published for callers outside this package — a host runtime driving its own mobile session, for instance. Import it from testmu_appium.perception; the same names are re-exported from the package root.

from testmu_appium.perception import (
    parse_tree, format_for_prompt, find_by_fingerprint, position_hint,
    EDITABLE_CLASSES, ROLE_MAP,
)

The binding owns this parser. V16, healing, and generated-test runtime all consume the public API above so document order and element identity have one definition. testmu_appium._helpers._tree remains an implementation detail.

parse_tree(xml_str, screen_w, screen_h) -> list[dict]

Parses an Appium page-source XML document into a flat list of useful on-screen nodes. A node is kept when it has a readable label, a resource id, or responds to touch; pure layout wrappers are skipped and their children promoted. Nodes are dropped when their bounds attribute is missing, zero-area, hidden, or outside the screen_w x screen_h viewport. Entries are de-duplicated on (role, name, center), first occurrence winning.

Every row carries interactive and depth. format_for_prompt filters to the interactive subset and assigns its own dense display numbering, preserving the visual-mode contract while text-mode consumers can reference informational rows.

Indices are 1-based. entry["index"] runs 1..len(result) over the returned list with no gaps, and that index is what the autoheal endpoint's dom_index refers to. Re-parsing a changed screen renumbers everything, so an index is only meaningful against the parse it came from.

Each entry carries exactly these keys:

screen_w / screen_h are the live window size in device pixels — the same units the bounds attribute uses.

format_for_prompt(elements) -> str

Renders the list from parse_tree as one line per entry, in the form a reasoning model reads: [<index>] <role> "<name>" [<states>] (<position>). Scrollable entries get a line noting that content may exist beyond the viewport. Returns "(no interactive elements detected — rely on the screenshot)" for an empty list.

find_by_fingerprint(elements, fp) -> dict | None

Re-finds a previously recorded element in a fresh parse_tree result. fp is a dict that may carry resource_id, text, content_desc and name; they are tried in that order, with resource_id + text preferred over resource_id alone. Returns the matching entry, or None when nothing matches.

ROLE_MAP

The ordered (class-name suffix, role) pairs parse_tree uses to assign role, matched by class.endswith(suffix), first match winning. A node matching no suffix becomes scrollable when its scrollable attribute is set, else item.

Platform support

Android ships today. iOS is accepted as configuration (platform="ios") so its arrival is a data event, but the iOS strategy column, keycode map and session-options row are not shipped yet and raise UnsupportedOnPlatform.

Development

pip install -e ".[dev]"
pytest -v

Tests are hermetic — no live device, no live grid, no live HTTP.