Testing your React Native App - The Cypress way
summary
Practical rundown: Cypress is used here as a JavaScript, non‑Selenium end-to-end runner that Thunkable uses to test React Native at the product level; the demo is a explained sample .spec.js not a full live build. Tests run in-browser via Expo for web to emulate mobile layouts, require Node 14+, record screenshots and videos on failure, and integrate with CI (GitHub Actions, CircleCI). Best practice is to target elements with data- attributes, component tests use a mount function, and Cypress supports Chrome/Firefox family browsers.
AI-written summary · about
chapters (12)
- 0:00Introduction to talk
- 1:25Agenda and Cypress overview
- 3:34Why Cypress stands out
- 5:42Cypress ecosystem explained
- 7:04Installing and setting up Cypress
- 8:26Understanding Cypress test structure
- 12:01End-to-end testing React Native
- 13:47Best practices for selectors
- 14:07Component testing frameworks
- 15:54HTTPS and CI support
- 16:38Cypress for Angular apps
- 17:20Closing and resources
related talks
26mIntegration Testing for React Native Apps
47mEnd to End Testing with Cypress
19mWhy you should Jest use Cypress for React component testing
40mReact Native is Coming – the story of hybrid mobile application testing
44mAutomation Testing Web Apps with Cypress
39mGaining Confidence with Cypress Tests
23mGaining Confidence with Cypress Tests
50mCypress, the Tool That Will Make You Love End-to-End Testing!
