skills.rest
Jose-Luis-Nunez
Jose-Luis-NunezCOMMUNITY
Explore all skills by this author →
GitHub

updating-ui-tests

Review and update XCUITest UI tests against project conventions.

2|1|Updated Apr 13, 2025
Search Tags:#automation#refactor#conventions#update#ui-tests#xcuitest#test-id
One-click install
npx skills add https://github.com/Jose-Luis-Nunez/FitnessApp --skill updating-ui-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: updating-ui-tests
Source: https://github.com/Jose-Luis-Nunez/FitnessApp/tree/main/.cursor/skills/updating-ui-tests
Command: npx skills add https://github.com/Jose-Luis-Nunez/FitnessApp --skill updating-ui-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams update, fix, and modernize existing XCUITest UI tests in the FitnessApp project, reducing flaky tests and aligning with current conventions.

Core Features & Use Cases

  • Review existing tests against the project conventions to identify structure, selectors, and API usage issues.
  • Apply fixes to modernize tests, replace raw APIs with DSL equivalents, and update test identifiers to match production AID constants.
  • Extend & maintain the test suite by adding missing steps for new UI elements and ensuring consistency with the references UI-test-conventions.

Quick Start

Open a failing UI test and follow the two-step workflow: review against conventions, then implement fixes to align with current patterns and identifiers.

Frequently Asked Questions about updating-ui-tests

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

FAQPage Schema
How do I update outdated XCUITest UI tests to fix flaky test failures?▼

Outdated XCUITest UI tests are modernized by reviewing production test code against project conventions, then applying fixes such as replacing raw APIs with DSL equivalents and updating test identifiers to reduce flakiness.

What is the best way to align XCUITest selectors with production test ID constants?▼

Aligning XCUITest selectors with production AID constants requires reviewing existing tests for structure and API usage, then updating test identifiers to match the production constants, ensuring consistent and reliable element location.

Can I use this workflow to refactor raw XCUITest API calls into a DSL?▼

Refactoring raw XCUITest API calls into a DSL is supported by first reviewing production test code to identify raw API usage, then applying fixes to replace those calls with DSL equivalents to align with current conventions.

Do I need existing UI-test-conventions to review and fix broken XCUITest suites?▼

Existing UI-test-conventions are required to review and fix broken XCUITest suites. The workflow explicitly reviews production test code against these reference conventions to identify structural and selector issues before applying fixes.

Why do my XCUITest UI tests keep failing after adding new UI elements?▼

XCUITest UI tests fail after adding new UI elements when missing steps or outdated identifiers are present. The workflow reviews tests against conventions and adds missing steps while updating test IDs to restore functionality.

Related Skills

Explore More Software Engineering Skills→
benaorbenaor
6

swift-testing-conventions

Document Swift and SwiftUI testing conventions for unit, integration, UI, and E2E tests.

Community
Advanced
Jose-Luis-NunezJose-Luis-Nunez
2

writing-ui-tests

Generate deterministic XCUITest UI tests for FitnessApp user flows.

Community
Intermediate
roncuevasroncuevas

ios-uitest

Generate iOS UI test suites using the Robot Pattern with accessibility identifiers.

Community
Intermediate
oxieoxie

implementation-phase

Enforce test-driven development and anti-duplication controls during implementation tasks.

Community
Intermediate