How React Native, Appium and me made each other shine!
summary
A React Native telecom app for Tella2 uses Appium + WebdriverIO + Cucumber with accessibility labels added via a single testProperties method so XPath drops to ~5% of selectors. Animations are disabled in an automation build (duration/delay → 0) saving ~9s per scenario; deep links and a test-link screen cut 15s by jumping straight to features; mocking real services with ng API mock saves ~8s and, by sending a unique device header to the mock server, enables parallel runs without state clashes. Sixty-five scenarios gain roughly 30 minutes total.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:40THE APP
- 4:04CP SELECTORS HYBRID SOLUTION
- 6:11ACCESSIBILITY LABEL(S)
- 6:58+ ACCESSIBILITY LABEL
- 10:43REMOVE ANIMATIONS
- 13:17MAGIC
- 15:57NEXT STEPS
- 16:39+ TEST STRATEGY
- 19:16+ TESTLINK SCREEN
- 25:33HEADER
- 27:19PHASE 3
- 30:34PRO'S AND CONS
related talks
30mTesting & React Native"Lessons from the Battlefield"
38mBuilding Your Own Native App Visual Testing Module with Appium
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
34mThe Restless Are Getting Native: Lessons Learned While Writing Automated Tests for an iOS App
39mPerformance issues: the usual suspects
18mTesting your React Native App - The Cypress way
