Testing
Testing for an Expo app, compared: Jest + Testing Library, or none - Expo Go support and what each option installs.
Hey - here's how testing works in ReadyNative. This category decides whether the tree ships a test runner - and every other module ships tests that live and die with it, so this is the safety net that makes swapping stacks cheap.
What stays the same: jest.config.js is a core file (the setup engine shares it) and stays in
place under both options, and each UI stack that needs one carries a jest setup file (src/components/ui/jest-setup.ts)
that jest.setup.ts requires. Swap with bun run setup --testing <option>.
- jest - the default. Jest on
jest-expowith React Native Testing Library and the mocks a real Expo app needs; core tests cover the stores, theme, env, the i18n shim, two kit primitives and the Settings screen. - none - no runner and no test files. Only pick it if you're bringing your own.
Options
One option per category - --testing <option> picks it:
bun run setup --testing jest