/course/xctest-espresso-strategies
XCTest & Espresso Strategies
Flake budgets, deterministic waits, and CI sharding without magical sleeps.
Overview
Parallelise UI tests, stub network at boundary layers, and read failure artifacts quickly. We discuss emulator vs device trade-offs honestly.
Included focus areas
- XCTestPlan matrices per device class
- Espresso IdlingResource patterns
- Stubbed DNS for integration suites
- Sharding math for GitHub Actions
- Screenshot/video capture on failure
- Accessibility audits in test pipelines
- Flake triage standup template
Outcomes
- Cut flake rate on sample suite by agreed metric
- Add one deterministic wait replacement
- Document CI shard strategy
Lead mentor
Paige Liu
Quality coach; built mobile CI for civic tech apps.
FAQ
Not included; local + emulator first.
Mentioned comparatively; focus is XCTest/Espresso.
Not supported; macOS required for XCTest portions.
Experience notes
“Espresso idling resource week fixed our checkout tests—still noisy on API 28, but we knew why.”