What problem does it solve?
Mobile UI regressions and layout defects are hard to detect across device states and physical hardware; this Skill provides a structured way to exercise screens, capture visuals, and produce deterministic layout assessments so teams can catch keyboard overlap, modal issues, and spacing defects before releases.
Core Features & Use Cases
- Screen-driven testing: Use ask_screen to list visible elements and obtain coordinates for reliable tap and swipe actions.
- Device control with UDID: Execute interactions (tap, swipe) targeted at specific devices to avoid conflicts and reproduce physical-device bugs.
- Visual QA integration: Inject expected layout context into visual-qa analysis to detect hidden elements, spacing defects, and deviations from design artifacts like Figma.
- Use Case: Verify that the submit button remains visible when the keyboard opens across multiple device orientations and OS versions.
Quick Start
Use the device-test skill to run a UI test case named login-keyboard on device UDID abc123 and verify that the submit button is not hidden by the keyboard.