vitest-nativeTest React Native with Vitest.

Zero config to first test ​

// vitest.config.ts
import { defineConfig } from 'vitest/config'
import { reactNative } from 'vitest-native'

export default defineConfig({
  plugins: [reactNative()],
})

// MyComponent.test.tsx
import { describe, it, expect } from 'vitest'
import { render, screen } from '@testing-library/react-native'
import { MyComponent } from './MyComponent'

describe('MyComponent', () => {
  it('renders correctly', () => {
    render(<MyComponent title="Hello" />)
    expect(screen.getByText('Hello')).toBeTruthy()
  })
})

reactNative() with no options resolves to the native engine — real React Native JS, mocking only the native boundary — whenever your project's Babel preset is present (i.e. any real RN app). No further setup.

Two engines, one plugin ​

vitest-native lets you choose the fidelity each suite needs — real React Native, or a fast mock — from one plugin:

Both engines share the same test API (RNTL, the helpers, the presets). A CI-gated cross-check keeps the mock behaviorally honest against real RN.

How it compares to Jest ​

Jest with @react-native/jest-preset is the React Native standard and works well. Reach for vitest-native when you value:

• Higher-fidelity option — Jest's RN preset and vitest-native both run real RN JS and mock the native side, but Jest mocks more (it swaps RN's core components and a few APIs for passthrough stand-ins). vitest-native's engine: 'native' mocks only the deeper native boundary, so your tests run RN's real component JS — or drop to a fast full mock when you don't need that. How the boundaries differ →
• DX — Vitest's watch mode, UI, and native ESM tooling.
• Unification — one runner if you also test web or server code with Vitest.

It is not primarily a speed play — choose it for the fidelity option and DX. Read the full comparison →

How it's verified ​

The reproducible guarantee is a CI-gated behavioral cross-check: a corpus of probes runs the same assertions under the mock engine and real React Native across React Native 0.81–0.86, and any divergence fails the build. Anyone can run it (bun run crosscheck), and the full corpus with its current pass count is published in the Fidelity Report. On top of that, the full CI gate runs lint, typecheck, build, and the mock + native + hot suites across an OS × Node matrix.

Pinned public apps are also run as external integration observations. They are useful tripwires, but their custom migration config, dependency changes, snapshots, and Jest-era shims mean their pass counts do not define vitest-native capability or fidelity. A change is reduced into a minimal package-owned test before it is classified. See the validation model.

Beta. Some APIs may still shift before 1.0. Maintained successor to vitest-community/vitest-react-native — same core idea, rebuilt for modern Vitest (v4).

Get started →