writing-xcuitests
This skill should be used when the user asks to "write XCUITest", "create UI tests", "fix flaky tests", "query XCUIElements", "implement Page Object pattern", or mentions XCUITest, UI testing for iOS/macOS apps. Targets experienced iOS developers who want best practices and efficiency improvements.
What this skill does
# Writing XCUITests
Guide for writing robust, maintainable XCUITests for iOS and macOS applications. This skill focuses on practical patterns, element querying strategies, and techniques to reduce test flakiness.
## Quick Start
### Element Queries
Prefer accessibility identifiers for reliable element queries:
```swift
// Best: Accessibility identifier
app.buttons["loginButton"].tap()
// Good: Text matching (fragile to localization)
app.buttons["Log In"].tap()
// Avoid: Index-based queries (brittle to UI changes)
app.buttons.element(boundBy: 0).tap()
```
Set accessibility identifiers in your app code:
```swift
button.accessibilityIdentifier = "loginButton"
```
Query by element type and identifier:
```swift
let emailField = app.textFields["emailField"]
let passwordField = app.secureTextFields["passwordField"]
let submitButton = app.buttons["submitButton"]
let statusLabel = app.staticTexts["statusLabel"]
```
### Common Interactions
**Tap elements:**
```swift
app.buttons["submitButton"].tap()
```
**Type text:**
```swift
app.textFields["emailField"].tap()
app.textFields["emailField"].typeText("[email protected]")
```
**Clear and type (preferred for input fields):**
```swift
let emailField = app.textFields["emailField"]
emailField.tap()
// Clear existing text by typing delete keys
if let value = emailField.value as? String, !value.isEmpty {
let deleteString = String(repeating: XCUIKeyboardKey.delete.rawValue,
count: value.count)
emailField.typeText(deleteString)
}
emailField.typeText("[email protected]")
```
**Toggle switches:**
```swift
let toggleSwitch = app.switches["notificationSwitch"]
if toggleSwitch.value as? String == "0" {
toggleSwitch.tap()
}
```
### Waiting for Elements
Always wait for elements before interacting:
```swift
let loginButton = app.buttons["loginButton"]
XCTAssertTrue(loginButton.waitForExistence(timeout: 5))
loginButton.tap()
```
Wait for element to disappear (loading indicators):
```swift
// Using expectation-based wait for disappearance
let spinner = app.activityIndicators["loadingSpinner"]
let predicate = NSPredicate(format: "exists == false")
let expectation = expectation(for: predicate, evaluatedWith: spinner)
wait(for: [expectation], timeout: 10)
```
Alternative simpler approach:
```swift
// Wait for element to disappear (simple polling approach)
let spinner = app.activityIndicators["loadingSpinner"]
let timeout: TimeInterval = 10
let startTime = Date()
while spinner.exists && Date().timeIntervalSince(startTime) < timeout {
Thread.sleep(forTimeInterval: 0.1)
}
XCTAssertFalse(spinner.exists, "Spinner did not disappear within timeout")
```
### Basic Assertions
Check element existence:
```swift
XCTAssertTrue(app.buttons["loginButton"].exists)
```
Check element properties:
```swift
let errorLabel = app.staticTexts["errorLabel"]
XCTAssertTrue(errorLabel.exists)
XCTAssertEqual(errorLabel.label, "Invalid credentials")
```
Check element state:
```swift
let submitButton = app.buttons["submitButton"]
XCTAssertTrue(submitButton.isEnabled)
XCTAssertTrue(submitButton.isHittable)
```
## Test Structure
### Basic XCTestCase Setup
```swift
import XCTest
class LoginTests: XCTestCase {
var app: XCUIApplication!
override func setUpWithError() throws {
continueAfterFailure = false
app = XCUIApplication()
app.launch()
}
override func tearDownWithError() throws {
app = nil
}
func testSuccessfulLogin() throws {
// Arrange
let emailField = app.textFields["emailField"]
let passwordField = app.secureTextFields["passwordField"]
let loginButton = app.buttons["loginButton"]
// Act
XCTAssertTrue(emailField.waitForExistence(timeout: 5))
emailField.tap()
emailField.typeText("[email protected]")
passwordField.tap()
passwordField.typeText("password123")
loginButton.tap()
// Assert
let welcomeLabel = app.staticTexts["welcomeLabel"]
XCTAssertTrue(welcomeLabel.waitForExistence(timeout: 5))
XCTAssertEqual(welcomeLabel.label, "Welcome back!")
}
}
```
### Launch Arguments and Environment Variables
Configure app state for testing:
```swift
override func setUpWithError() throws {
continueAfterFailure = false
app = XCUIApplication()
// Pass launch arguments
app.launchArguments = ["--uitesting", "--reset-data"]
// Set environment variables
app.launchEnvironment = [
"MOCK_API": "true",
"ANIMATION_SPEED": "0"
]
app.launch()
}
```
## Reference Documentation
For detailed guidance on specific topics:
| Topic | Reference File |
|-------|---------------|
| Element Query Strategies | [reference/element-queries.md](reference/element-queries.md) |
| Interactions & Gestures | [reference/interactions.md](reference/interactions.md) |
| Waiting & Synchronization | [reference/waiting.md](reference/waiting.md) |
| Assertions & Validation | [reference/assertions.md](reference/assertions.md) |
| Page Object Pattern | [reference/page-objects.md](reference/page-objects.md) |
| Advanced Gestures | [reference/gestures.md](reference/gestures.md) |
| Fixing Flaky Tests | [reference/flaky-tests.md](reference/flaky-tests.md) |
| Complete Examples | [reference/examples.md](reference/examples.md) |
## Key Principles
1. **Use accessibility identifiers** - Most reliable query method
2. **Always wait for elements** - Use `waitForExistence(timeout:)` before interactions
3. **Test behavior, not implementation** - Focus on user-visible outcomes
4. **Keep tests independent** - Each test should run in isolation
5. **Use Page Objects** - Encapsulate screen structure and reduce duplication
6. **Minimize sleeps** - Prefer explicit waits over `sleep()` calls
7. **Handle animations** - Disable or account for UI animations in tests
8. **Verify preconditions** - Assert element state before interactions
## Common Patterns
**Login flow:**
```swift
func login(email: String, password: String) {
let emailField = app.textFields["emailField"]
let passwordField = app.secureTextFields["passwordField"]
let loginButton = app.buttons["loginButton"]
XCTAssertTrue(emailField.waitForExistence(timeout: 5))
emailField.tap()
emailField.typeText(email)
passwordField.tap()
passwordField.typeText(password)
loginButton.tap()
}
```
**Navigate and verify:**
```swift
func testNavigationToSettings() {
// Navigate
app.tabBars.buttons["Settings"].tap()
// Verify arrival
let settingsTitle = app.navigationBars["Settings"]
XCTAssertTrue(settingsTitle.waitForExistence(timeout: 3))
}
```
**Form submission with validation:**
```swift
func testFormValidation() {
let nameField = app.textFields["nameField"]
let submitButton = app.buttons["submitButton"]
// Submit empty form
submitButton.tap()
// Verify validation message
let errorLabel = app.staticTexts["nameErrorLabel"]
XCTAssertTrue(errorLabel.waitForExistence(timeout: 2))
XCTAssertEqual(errorLabel.label, "Name is required")
// Fix and resubmit
nameField.tap()
nameField.typeText("John Doe")
submitButton.tap()
// Verify error cleared
XCTAssertFalse(errorLabel.exists)
}
```
## Next Steps
- Implement Page Objects for complex screens: [reference/page-objects.md](reference/page-objects.md)
- Learn advanced gestures (swipe, pinch, rotate): [reference/gestures.md](reference/gestures.md)
- Debug flaky tests: [reference/flaky-tests.md](reference/flaky-tests.md)
- Review complete test examples: [reference/examples.md](reference/examples.md)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.