Espresso Setup Workflow
Routing
Prepare only the Espresso route. Use driver-specific official guidance for an
existing Espresso runtime failure after setup passes. Load FFmpeg or bundletool
only when the user explicitly requested that capability.
Required inputs
Confirm Android as the target, global appium mode or explicitly requested
local npx appium mode, host OS, device or emulator expectations, permissions,
and optional dependency requests.
Workflow
- Load the global command profile by default or the local profile only when
explicitly requested.
- Load the Android profile, shared Appium setup basics, and Android emulator
setup Context.
- Load the Espresso decision, installation, doctor, and smoke references in
that order.
- Run
node tools/appium/setup/scripts/check-espresso-env.mjs --format summary --report auto; add
--appium-mode local only for explicitly requested local mode. Require
top-level summary.requiredOk: true.
Apply required fixes in technical dependency order and rerun affected checks.
If the gate remains unresolved, report blocked with evidence and the next
action. Load the matching example only when needed.
- Verify the direct doctor output reports
0 required fixes needed using
appium driver doctor espresso, or
npx --no-install appium driver doctor espresso in local mode.
- Run
node tools/appium/setup/scripts/smoke-appium-server.mjs --driver espresso --report auto;
add --appium-mode local only in local mode. Require
summary.requiredOk: true for server readiness, driver evidence, and
cleanup. The smoke reference documents target-specific options.
Espresso setup safety and approval constraints
- Preserve the selected command mode and working Java, Android SDK, device,
emulator, and Espresso installations.
- Ask before optional FFmpeg or bundletool setup, privileged commands, SDK
license changes, Espresso build changes, or emulator creation that changes
local state.
Completion criteria
- Android environment completion criteria pass.
- Appium succeeds in the selected command mode.
- The installed driver list includes
espresso.
appium driver doctor espresso reports 0 required fixes needed; optional
warnings are non-blocking./status succeeds, server logs list espresso, and the server
started for verification has exited.
Evidence boundary
Report Appium and Espresso versions, helper requiredOk, Android prerequisite
summary, doctor required/optional summary, /status, server driver evidence,
cleanup, and explicitly requested optional capability results.
Self-Improvement Prompt
Before the final response, report any missing, ambiguous, outdated, or
retry-causing Espresso setup instruction with its asset path and proposed
wording. Leave unrelated assets unchanged.
1---2name: setup-espresso3description: Prepare and verify Appium Espresso by validating Node/Appium, Android SDK and Java prerequisites, driver installation, doctor output, and server smoke evidence. Use after the setup Skill selects Espresso. Do not use for an existing Espresso runtime failure after prerequisites pass; this repository does not provide that troubleshooting workflow.4---56# Espresso Setup Workflow78## Routing910Prepare only the Espresso route. Use driver-specific official guidance for an11existing Espresso runtime failure after setup passes. Load FFmpeg or bundletool12only when the user explicitly requested that capability.1314## Required inputs1516Confirm Android as the target, global `appium` mode or explicitly requested17local `npx appium` mode, host OS, device or emulator expectations, permissions,18and optional dependency requests.1920## Workflow21221. Load the global command profile by default or the local profile only when23 explicitly requested.242. Load the Android profile, shared Appium setup basics, and Android emulator25 setup Context.263. Load the Espresso decision, installation, doctor, and smoke references in27 that order.284. Run `node tools/appium/setup/scripts/check-espresso-env.mjs --format summary --report auto`; add29 `--appium-mode local` only for explicitly requested local mode. Require30 top-level `summary.requiredOk: true`.31 Apply required fixes in technical dependency order and rerun affected checks.32 If the gate remains unresolved, report `blocked` with evidence and the next33 action. Load the matching example only when needed.345. Verify the direct doctor output reports `0 required fixes needed` using35 `appium driver doctor espresso`, or36 `npx --no-install appium driver doctor espresso` in local mode.376. Run `node tools/appium/setup/scripts/smoke-appium-server.mjs --driver espresso --report auto`;38 add `--appium-mode local` only in local mode. Require39 `summary.requiredOk: true` for server readiness, driver evidence, and40 cleanup. The smoke reference documents target-specific options.4142## Espresso setup safety and approval constraints4344- Preserve the selected command mode and working Java, Android SDK, device,45 emulator, and Espresso installations.46- Ask before optional FFmpeg or bundletool setup, privileged commands, SDK47 license changes, Espresso build changes, or emulator creation that changes48 local state.4950## Completion criteria5152- Android environment completion criteria pass.53- Appium succeeds in the selected command mode.54- The installed driver list includes `espresso`.55- `appium driver doctor espresso` reports `0 required fixes needed`; optional56 warnings are non-blocking.57- `/status` succeeds, server logs list `espresso`, and the server58 started for verification has exited.5960## Evidence boundary6162Report Appium and Espresso versions, helper `requiredOk`, Android prerequisite63summary, doctor required/optional summary, `/status`, server driver evidence,64cleanup, and explicitly requested optional capability results.6566## Self-Improvement Prompt6768Before the final response, report any missing, ambiguous, outdated, or69retry-causing Espresso setup instruction with its asset path and proposed70wording. Leave unrelated assets unchanged.
appium