Alternatives to XCUITest, or Why and How Developers Should Write Automated Tests
summary
Talk covers writing automated tests for iOS beyond XCUITest, arguing developers (not just QA) should write tests. It compares approaches including enhanced unit tests and the KIF framework, explains white-box testing of multithreaded code, and shows when to use alternatives to XCUI to reduce flaky tests for teams and indie developers.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:29Why write automated tests
- 2:52Automation scope in mobile banking
- 4:35XCUITest and UI testing problems
- 9:10Criteria for good automated tests
- 11:38Integration tests on steroids
- 15:35Choosing test components
- 20:08KIF framework overview
- 24:01Writing a KIF test
- 26:11How KIF finds elements
- 29:10Multithreading optimization in tests
- 33:28Page Object pattern for UI tests
- 35:15UI testing with KIF
- 37:44KIF test example
- 39:06KIF with SwiftUI nuances
- 40:50Improving KIF tests
- 41:51KIF limitations and downsides
- 42:54Test speed comparison
- 44:20Summary and recommendations
related talks
41mOvercoming XCUITest pain to bring UITests to iOS apps
37miOS Test Automation to Infinity and Beyond
44mGetting started with #XCUITests
32mUI Automation with XCUITest
28mAdvanced Techniques in iOS UI Testing
55mAutomated Testing in an iOS Project: The ICQ Case
23mWhy testing is also a developer's problem
54mTest Driven Development (TDD) by Controlling Dependencies