The Restless Are Getting Native: Lessons Learned While Writing Automated Tests for an iOS App
summary
Details how a test suite is built for a native iOS app: chooses NativeDriver with the familiar WebDriver API, writes tests in Java, and embeds an embedded HTTP server inside the app to receive commands; runs tests via xcodebuild plus helper launchers like ios-sim or wax-sim; wires tests into continuous integration (TeamCity/Jenkins/Cruise) to run on commit and locally for fast feedback. Notes cultural pitfalls—separate automation teams, wrong language choice—and recommends embedding automation engineers, showing value early, and keeping most checks at unit level.
AI-written summary · about
chapters (7)
- 0:00The importance of feedback
- 1:17Automation feedback loops
- 7:28Organizational team structure
- 10:47Native mobile automation
- 19:28Cultural and language barriers
- 24:27Recommendations for success
- 28:30Future of mobile testing
related talks
30mTesting & React Native"Lessons from the Battlefield"
50mMobile app test automation: product company experience
38mBuilding Your Own Native App Visual Testing Module with Appium
33mHow React Native, Appium and me made each other shine!
40mReact Native is Coming – the story of hybrid mobile application testing
15mChoose a Mobile Test Automation Framework That Suits Your Team
26mIntegration Testing for React Native Apps
31mDetox: Tackling the Flakiness of Mobile Automation