No test runner
The "No test runner" option of the ReadyNative Expo template: no jest; module tests are removed.
Expo Go: yes
Runs in Expo Go; no dev build needed for this module.
No Jest, no test files. I'd only choose this if you're bringing a different runner or genuinely won't write tests - every other module ships tests that vanish with this option, so you lose the safety net that makes swapping stacks cheap. Setup removes jest.setup.ts, every src/**/__tests__/** file (core and module-owned, through removeFiles) and the Jest dev dependencies.
Setup
bun run setup --testing noneThat's it - there's nothing to configure. jest.config.js stays behind: it's a core file shared with the setup engine, and it's harmless without a runner.
Usage
Nothing to run. bun run lint and npx tsc --noEmit still cover the tree, and bun run doctor still checks your configuration.
Gotchas
- Changing your mind is one command:
bun run setup --testing jestbrings back the setup file, the core tests and the dev dependencies. Module-owned tests come back with their modules.
Reference
Everything below is generated from modules/testing/none/module.json - the same file bun run setup reads, so it is what actually lands in your repo.
Install
bun run setup --testing noneModule id: testing/none.