software-mansion/argent

argent-test-ui-flow

Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/software-mansion/argent --skill argent-test-ui-flow

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

Before testing

Resolve the device first: call list-devices, use the platform the user named or else prefer a device that is already running, and don't pick a cabled phone without explicit intent. Setup: argent-ios-simulator-setup / argent-android-emulator-setup. The interaction tool names are identical on iOS and Android.

Physical iPhone (kind: "device"): read argent-ios-device-interact first. launch-app before anything; describe fails while the app is backgrounded.

1. Workflow

For implementation tasks that modify visible UI, this workflow also serves as a visual acceptance path.

  1. Baseline screenshot: call screenshot to see the current UI state. For visual regression comparison or UI change verification, capture the baseline at scale: 1.0 with includeImageInContext: false and keep the returned path before editing whenever feasible.
  2. Find target: get element coordinates from a discovery tool before tapping:
  • App screens (React Native included), in-app modals and system dialogs: describe. Fall back to screenshot only if an overlay is not exposed reliably. When the app raises its own permission dialog, answer it here; that's the real flow under test. To take a prompt out of the flow, use argent-settings-permissions during setup.
  1. Interact: perform the action (gesture-tap, gesture-swipe, keyboard, button, ...); you receive a screenshot and element tree automatically (an identical earlier tree is named by its Tree id, not repeated).
  2. Verify: check the returned screenshot. If it shows a loading/transitional state, block with await-ui-element (expected element visible, or a spinner hidden) rather than a guessed delay (its result carries the new screenshot and element tree), but only with a selector you can trust (text/identifier/role) that the screen is known to have or that you saw in a prior describe; a guessed one just times out. Otherwise use a short fixed wait. Pick evidence by what's being asserted:
  • Visual (layout, spacing, color, typography, image/icon rendering, clipping, overflow, text rendering): prefer screenshot-diff against the step 1 baseline: it surfaces pixel-visible changes the auto-screenshot might miss. Fall back to inspecting the auto-screenshot only when a stable baseline isn't available.
  • Structural (navigation state, element existence, accessibility labels/values, selection, hierarchy, route): verify with describe or debugger-component-tree.
  • Runtime / log / network (console errors, API calls, persistence, timing): verify with view-network-logs, debugger-log-registry, debugger-evaluate, or targeted tests. A not_connected result from the debugger tools is not evidence about the app: follow its guidance, then re-verify.
  • Mixed: collect evidence for each relevant class.
  • Report the combined verdict: expected behavior, observed behavior, evidence used, and any blocker for requested visual diffing.
  1. Repeat for each step in the flow.

2. Example: login flow

1. describe → login screen
2. gesture-tap email field (frame centre from the tree)
3. keyboard { text: "user@example.com" }
4. gesture-tap password field (from the returned tree)
5. run-sequence: keyboard { text: "{{secret:APP_PASSWORD}}" }, gesture-tap Login button
6. await-ui-element → home screen appeared
Credentials: never type plaintext credentials; use a {{secret:<NAME>}} placeholder (keyboard's text parameter lists where it is read from and what to do when a name is missing). Never invent credentials or echo secret values into reports or saved files.

3. Recovery Pattern

  • Screen mid-transition or loading: wait with await-ui-element as in step 4, then re-check. Fall back to a fixed wait + screenshot only when no element reliably marks the transition. Don't poll with repeated screenshots.
  • Tap misses the target: re-run describe and retry once with new coordinates. If it fails twice, stop and report that the element was not found.
  • Permission dialog or modal visible: re-run describe first. Stay in screenshot-driven navigation only while the overlay is not exposed reliably: tap one visible button at a time, verify with the returned screenshot, and switch back to describe as soon as it is dismissed.
  • A saved e2e test fails during e2e-execute replay (as opposed to the live steps above): follow argent-create-e2e's Diagnose a replay failure: classify the failure, inspect the actual screen, repair the smallest justified unit, then replay the full e2e test.

Record for replay: if a tested flow is likely to be repeated, use the argent-create-e2e skill to record it as a .yaml test, so it can be replayed later with a single e2e-execute call.

Related Skills

SkillWhen to use
argent-device-interactTool usage for tapping, swiping, typing (iOS + Android)
argent-screenshot-diffVisual regression and before/after screenshot comparison
argent-ios-simulator-setupBooting and connecting an iOS simulator
argent-android-emulator-setupBooting and connecting an Android emulator
argent-react-native-app-workflowStarting the app, Metro, build issues
argent-metro-debuggerConsole logs, JS evaluation, component inspection
argent-create-e2eRecord a test sequence as a replayable e2e test
z tego samego repozytorium

Więcej Skills

Wszystkie Skills
software-mansion
Społeczność

argent-android-emulator-setup

Set up and connect to an Android emulator using argent MCP tools. Use when starting a new session on Android, booting an emulator, getting a device serial, or before any UI interaction task.

Instalacje / 1h
6
GitHub Stars
3,2 tys.
Aktualizacja
19 lis
software-mansion
Społeczność

argent-create-e2e

Create, record, edit, replay, or repair reusable Argent e2e test YAML files. Use when the user asks to record, replay, or run an e2e test or a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-e2e. Also use before repeating three or more interactions. For one-off UI checks, acceptance-driven regression tests, or screen video, use argent-test-ui-flow, argent-qa-e2e, or argent-screen-recording respectively.

Instalacje / 1h
6
GitHub Stars
3,2 tys.
Aktualizacja
19 lis
software-mansion
Społeczność

argent-device-interact

Interact with an iOS simulator or iPhone, Android emulator or phone, or Chromium (CDP) app using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling/swiping, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots, waiting for an element to appear or disappear, or checking visible app state after interactions. Not for TV targets.

Instalacje / 1h
6
GitHub Stars
3,2 tys.
Aktualizacja
19 lis
software-mansion
Społeczność

argent-ios-device-interact

Drive a physical iPhone through argent. Use when a physical iPhone is involved (a list-devices iOS entry with kind "device") and ONLY then; never for a simulator. For cable, trust, or signing problems read argent-ios-device-setup.

Instalacje / 1h
6
GitHub Stars
3,2 tys.
Aktualizacja
19 lis