skills.rest
Seyamalam
SeyamalamCOMMUNITY
Explore all skills by this author →
Website𝕏@SeyamAlam1GitHub

argent-test-ui-flow

Automates UI testing on iOS and Android devices through interact-screenshot-verify loops using argent MCP tools.

Updated Aug 29, 2026
Search Tags:#ui testing#end-to-end testing#mcp tools#mobile automation#ios simulator#android emulator#screenshot verification
One-click install
npx skills add https://github.com/Seyamalam/pstu_final --skill argent-test-ui-flow-seyamalam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: argent-test-ui-flow
Source: https://github.com/Seyamalam/pstu_final/tree/main/.agents/skills/argent-test-ui-flow
Command: npx skills add https://github.com/Seyamalam/pstu_final --skill argent-test-ui-flow-seyamalam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying UI flows on mobile apps is slow and error-prone. This Skill autonomously drives an iOS simulator or Android emulator through tap, swipe, and type interactions, capturing screenshots and structural evidence at each step to verify that login flows, navigation, and visual changes behave as expected. ## Core Features & Use Cases - Interact-screenshot-verify loops: Tap, swipe, type, and press buttons via argent MCP tools, then verify each step with auto-returned screenshots, accessibility trees, or component trees. - Multi-class evidence collection: Classify expected results as visual, structural, runtime/log/network, or mixed, then gather matching evidence with screenshot-diff, describe, debugger-component-tree, or network log tools. - Cross-platform support: Works on both iOS simulators and Android emulators with identical tool names, auto-dispatching based on the device UDID. - Use Case: Verify a login flow end-to-end by tapping the email field, entering credentials via secret placeholders, tapping Login, and confirming the home screen appears, with screenshot evidence at every step. ## Quick Start Test the login flow of my app on the running Android emulator and verify the home screen appears after entering credentials.

Frequently Asked Questions about argent-test-ui-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a mobile app UI flow automatically?▼

Run an interact-screenshot-verify loop: take a baseline screenshot, locate elements with describe or debugger-component-tree, perform gestures like gesture-tap or keyboard input, then verify the returned screenshot matches expectations. Repeat for each step in the flow.

How to find element coordinates before tapping on iOS or Android?▼

Use debugger-component-tree for React Native apps, which returns component names with tap coordinates. For standard screens use describe, which returns the accessibility tree on iOS and the uiautomator tree on Android. Screenshot-based estimation is the fallback.

Does this UI testing approach work on both iOS and Android?▼

Yes, the interaction tool names are identical on both platforms, including gesture-tap, gesture-swipe, describe, and screenshot. The tool server auto-dispatches based on the udid you pass: UUID-shaped identifiers route to iOS, adb serials route to Android.

How do I handle loading spinners during UI test automation?▼

Use await-ui-element to block until a known element becomes visible or a spinner becomes hidden, rather than guessing fixed delays. Only use selectors you have confirmed exist through a prior describe call, otherwise the wait will time out.

How do I enter passwords during automated UI testing safely?▼

Use a {{secret:<NAME>}} placeholder in the keyboard tool, which is resolved server-side from ARGENT_SECRET_ environment variables or .argent/secrets.env files. The secret value never enters the agent context, and missing names produce an error listing available options.

What should I do when a tap misses its target during UI testing?▼

Re-run the discovery tool such as describe or debugger-component-tree to get fresh coordinates, then retry once. If the tap fails twice at the same coordinates, stop, re-discover the element, and report if it cannot be found.

Related Skills

Explore More Software Engineering Skills→
s-iwasaki-bs-iwasaki-b

debug-run

Build and install debug builds on Android emulators and iOS simulators.

Community
Advanced
softwarebyzesoftwarebyze

argent-create-flow

Record simulator or UI interaction workflows as replayable YAML MCP tool-call sequences.

Community
Intermediate
EvolutionAPIEvolutionAPI
520

dev-visual-verdict

Compare before and after screenshots to detect visual regressions in UI components.

Official
Intermediate
alkofualkofu
3

write-reliable-tests

Implement deterministic unit, integration, or end-to-end tests with setup, mocks, and cleanup.

Community
Advanced