Overcoming XCUITest pain to bring UITests to iOS apps
summary
This session explains how to introduce automated UI (E2E) tests for iOS apps using Apple’s XCUITest framework to reduce manual-testing cost as a product grows. It covers practical techniques and know-how for working with XCUITest (including how to operate UI components), and recommends using the Page Object design pattern and team-aligned implementation policies to keep tests reusable; it also notes that read-only verification tests are easier while tests that change user state are harder to implement.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:29XCUITest breakage causes
- 5:01Merpay release timeline
- 7:38UI test intro
- 8:45Choosing XCUITest
- 10:38XCUITest basics
- 17:03Page Object pattern
- 26:19XCUITest tips & pitfalls
- 35:30CI UI test ops
- 40:20Summary
related talks
32mUI Automation with XCUITest
44mGetting started with #XCUITests
46mAlternatives to XCUITest, or Why and How Developers Should Write Automated Tests
37miOS Test Automation to Infinity and Beyond
48mUI Tests in an iOS Project
28mAdvanced Techniques in iOS UI Testing
29mThe Magic of UI Testing
23mUI Testing for Fun and Profit