Developing and testing permissions flows
summary
Describes building a singleton permissions helper for camera, photo library and microphone with dependency injection, plus a small photo wrapper and 13 unit tests that verify alert logic. Explains why KIF isn’t enough, why real devices are required, and how XCUITest uses a XCUITest interruption monitor to handle system alerts while UI recording finds element identifiers. Details include fake alerts that deep‑link to Settings, the app relaunching back to the feed, and trade‑offs made to balance UX and test coverage.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:35How we implemented it
- 6:01The second problem
- 7:53The solution
- 9:19What are permissions alerts
- 10:17Fake alerts vs real alerts
- 13:15Design best practices
- 17:31Simulator limitations
- 19:31UI interruption monitor
- 21:40Fake alerts
- 22:46Scenario tests
- 25:18Outro
related talks
43mThe importance of privacy
46mAlternatives to XCUITest, or Why and How Developers Should Write Automated Tests
44mGetting started with #XCUITests
32mUI Automation with XCUITest
23mEnhancing App Experiences with App Intents and Live Activities
23mAppium: Under the Hood of WebDriverAgent
55mAutomated Testing in an iOS Project: The ICQ Case
48mUI Tests in an iOS Project