Automate iOS UI tests with condition-based waits and interaction recording.
npx skills add https://github.com/derKlinke/codex-config --skill ui-testing-derklinke
Please help me install this Agent Skill. Skill: ui-testing Source: https://github.com/derKlinke/codex-config/tree/main/skills/ios-ui-testing Command: npx skills add https://github.com/derKlinke/codex-config --skill ui-testing-derklinke
This Skill helps engineers stabilize iOS UI tests by reducing flakiness through condition-based waiting, avoiding arbitrary sleeps, and enabling reliable recording workflows.
Start a new UI Test target in Xcode, enable the Recording UI Automation workflow, and begin recording a user journey to capture stable queries and assertions.
High-intent search queries and answers about installing and using this skill.
To stop XCTest UI tests from being flaky, replace arbitrary sleeps and fixed timeouts with condition-based waiting patterns. This ensures tests only proceed when specific UI conditions are met, improving reliability across different iOS devices and OS versions.
Recording UI automation sessions in Xcode 26 captures your interactions and generates reusable Swift test code. You start a new UI Test target, enable the recording workflow, and perform a user journey to automatically create stable queries and assertions for replay.
Yes, condition-based wait patterns require access to accessibility identifiers. Using accessibility-first testing patterns allows the framework to reliably locate UI elements, generate stable queries, and perform built-in accessibility auditing during your test runs.
The best way to diagnose flaky UI tests is using built-in debugging aids like video review and overlays. Additionally, you can run multi-configuration test plans with network conditioning to surface timing-related issues early and analyze failures across multiple devices and languages.
Yes, you can use network conditioning to surface timing-related issues in iOS UI testing. By applying multi-configuration test plans and simulating various network conditions, you can identify and resolve timing-related flakiness before it impacts users.
Yes, you need an Xcode UI testing target to automate reliable iOS UI tests. Setting up a dedicated testing target is a prerequisite to enable cross-device recording, condition-based waiting, and network-conditioned scenarios for your XCTest-based UI tests.
pradeepmouliReplace arbitrary waits with condition-based waiting in Xcode UI tests.
CharlesWiltgenAutomate iOS UI tests with condition-based waiting and accessibility patterns.
tuliopc23Record and enhance Xcode UI tests with accessibility identifiers and explicit waits.
rileyhilliardReplace arbitrary test delays with condition-based waiting patterns.
