Achieving Higher Test Coverage: Our Approach to UI Testing on iOS
Article Summary
Aliou Sarr from leboncoin reveals how shifting UI test ownership from QA to developers doubled their test count in under a year. The result? A 99.6% crash-free iOS app serving 28 million monthly users.
With 40 iOS developers shipping weekly releases across 50 modules, leboncoin faced a testing bottleneck. Their QA team wrote UI tests after features shipped, causing delays and missed regressions. They redesigned their entire approach to put developers back in control.
Key Takeaways
- Moved UI test ownership from QA to developers during feature development
- Built TestKit framework to wrap XCTest and simplify test writing
- Auto-sync test results with QA test plans using unique IDs
- Support multiple test configurations (logged in/out) via environment variables
- Doubled UI test count, achieved 99.6% crash-free rate
Critical Insight
By giving developers ownership of UI tests and building a custom framework to simplify XCTest, leboncoin doubled their test coverage and hit 99.6% crash-free sessions.
