From 6ed00abc1efe5a00bc28654cd9d117222e6adb78 Mon Sep 17 00:00:00 2001 From: Ayaan Zaidi Date: Fri, 27 Feb 2026 11:44:48 +0530 Subject: [PATCH] docs: document android capability sweep in testing guide --- docs/help/testing.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/help/testing.md b/docs/help/testing.md index 01bb80abb47..8eb7f86277b 100644 --- a/docs/help/testing.md +++ b/docs/help/testing.md @@ -101,6 +101,23 @@ Use this decision table: - Touching gateway networking / WS protocol / pairing: add `pnpm test:e2e` - Debugging “my bot is down” / provider-specific failures / tool calling: run a narrowed `pnpm test:live` +## Live: Android node capability sweep + +- Test: `src/gateway/android-node.capabilities.live.test.ts` +- Script: `pnpm android:test:integration` +- Goal: invoke **every command currently advertised** by a connected Android node and assert command contract behavior. +- Scope: + - Preconditioned/manual setup (the suite does not install/run/pair the app). + - Command-by-command gateway `node.invoke` validation for the selected Android node. +- Required pre-setup: + - Android app already connected + paired to the gateway. + - App kept in foreground. + - Permissions/capture consent granted for capabilities you expect to pass. +- Optional target overrides: + - `OPENCLAW_ANDROID_NODE_ID` or `OPENCLAW_ANDROID_NODE_NAME`. + - `OPENCLAW_ANDROID_GATEWAY_URL` / `OPENCLAW_ANDROID_GATEWAY_TOKEN` / `OPENCLAW_ANDROID_GATEWAY_PASSWORD`. +- Full Android setup details: [Android App](/platforms/android) + ## Live: model smoke (profile keys) Live tests are split into two layers so we can isolate failures: