axiom-ui-testing

Replace arbitrary sleeps with condition-based waiting in XCTest/XCUITest UI tests.

3|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/harivansh-afk/claude-code-vertical --skill axiom-ui-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-ui-testing
Source: https://github.com/harivansh-afk/claude-code-vertical/tree/main/skill-index/skills/axiom-ui-testing
Command: npx skills add https://github.com/harivansh-afk/claude-code-vertical --skill axiom-ui-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI tests are prone to flakiness from timing and device variation. Axiom UI Testing provides patterns and practices to make UI automation reliable, record interactions, and review results across devices and languages.

Core Features & Use Cases

  • Condition-based waiting to eliminate arbitrary sleeps and flaky results
  • Recording UI Automation sessions in Xcode 26 with playback across devices and languages
  • Accessibility identifiers best practices for stable selectors
  • Multi-configuration test plans for device size and network profiles
  • Video and screenshot capture for CI/cloud environments

Quick Start

Create a UI Testing Bundle in your Xcode project, enable accessibility identifiers for interactive elements, and use Xcode 26's recording to generate initial test code. Then refine selectors to prefer identifiers over labels and run tests locally or in Xcode Cloud across configurations.

Frequently Asked Questions about axiom-ui-testing

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

FAQPage Schema
How do I fix flaky XCUITest UI tests caused by arbitrary sleeps?

Stabilize flaky XCUITest automation by replacing arbitrary sleeps with condition-based waiting. This ensures tests wait for specific UI states, eliminating timing flakiness across devices and CI environments.

How do I record UI automation sessions in Xcode 26 for playback across devices?

Record UI automation sessions in Xcode 26 to generate initial test code. Refine selectors using accessibility identifiers to enable reliable playback across devices, languages, and CI environments.

Why should I use accessibility identifiers instead of labels for XCUITest selectors?

Use accessibility identifiers instead of labels for XCUITest selectors to maintain stable element targeting. Labels can change across languages, whereas identifiers remain constant, ensuring reliable cross-device test execution.

Can I run XCUITest automation across multiple device sizes and network profiles?

Run XCUITest automation across multiple device sizes and network profiles using multi-configuration test plans. This approach validates app behavior under various conditions locally and in Xcode Cloud.

How do I capture video and screenshots during Xcode Cloud UI testing?

Capture video and screenshots during Xcode Cloud UI testing to review automation results. This provides visual evidence of test execution across configurations, aiding debugging for CI environments.