How do I install the React Native Testing skill?

Run npx skillmds@latest add maikotrindade/react-native-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is React Native Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with React Native Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is React Native Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published React Native Testing?

maikotrindade (@maikotrindade) published this skill. Their other Agent Skills are listed on their SkillMD profile.

React Native Testing by maikotrindade

Name: React Native Testing
Rating: 4.5 (4 reviews)
Author: maikotrindade

File contents

React Native Testing Library

Deep API reference for @testing-library/react-native v13 and v14.

Scope: unit + component tests with Jest + RNTL. For end-to-end UI flows on real devices/simulators, use Maestro — declarative YAML flows, no code, runs against the built app. RNTL and Maestro are complementary, not alternatives.

IMPORTANT: API signatures, sync/async behavior, and available functions differ between v13 and v14. Always check the project's package.json and load the matching version reference rather than relying on memorized patterns.

Version Detection

Check @testing-library/react-native in package.json:

v14.x → load reference-v14-api (React 19+, async APIs, test-renderer)
v13.x → load reference-v13-api (React 18+, sync APIs, react-test-renderer)

Core References

Topic	Description	Reference
Core patterns	Query priority, render/screen, userEvent vs fireEvent, waitFor, 11 core rules	core-patterns
v13 API (React 18)	Sync render, full method tables, fireEvent sync, React 19 compat shims	reference-v13-api
v14 API (React 19)	Async render, await-based APIs, removed APIs, v13→v14 migration codemods	reference-v14-api
Anti-patterns	Wrong queries, waitFor misuse, unnecessary act, destructuring, missing await	best-practices-anti-patterns

Key Recommendations

Always use screen for queries — never destructure from render()
getByRole first with { name: '...' } option (most accessibility-aware)
findBy* for async elements — not waitFor + getBy*
userEvent over fireEvent — more realistic interaction simulation
queryBy* only for non-existence assertions (.not.toBeOnTheScreen())
v14: always await every API (including render, fireEvent, act)

---name: react-native-testingdescription: Deep React Native Testing Library (RNTL) reference — v13 (React 18 sync) and v14 (React 19 async), queries, userEvent, matchers, anti-patterns.---# React Native Testing Library> Deep API reference for `@testing-library/react-native` v13 and v14.>> **Scope:** unit + component tests with Jest + RNTL. For end-to-end UI flows on real devices/simulators, use **[Maestro](https://maestro.mobile.dev/)** — declarative YAML flows, no code, runs against the built app. RNTL and Maestro are complementary, not alternatives.**IMPORTANT:** API signatures, sync/async behavior, and available functions differ between v13 and v14. Always check the project's `package.json` and load the matching version reference rather than relying on memorized patterns.## Version DetectionCheck `@testing-library/react-native` in `package.json`:- **v14.x** → load [reference-v14-api](references/reference-v14-api.md) (React 19+, async APIs, `test-renderer`)- **v13.x** → load [reference-v13-api](references/reference-v13-api.md) (React 18+, sync APIs, `react-test-renderer`)## Core References| Topic | Description | Reference ||-------|-------------|-----------|| Core patterns | Query priority, render/screen, userEvent vs fireEvent, waitFor, 11 core rules | [core-patterns](references/core-patterns.md) || v13 API (React 18) | Sync render, full method tables, fireEvent sync, React 19 compat shims | [reference-v13-api](references/reference-v13-api.md) || v14 API (React 19) | Async render, await-based APIs, removed APIs, v13→v14 migration codemods | [reference-v14-api](references/reference-v14-api.md) || Anti-patterns | Wrong queries, waitFor misuse, unnecessary act, destructuring, missing await | [best-practices-anti-patterns](references/best-practices-anti-patterns.md) |## Key Recommendations- **Always use `screen`** for queries — never destructure from `render()`- **`getByRole` first** with `{ name: '...' }` option (most accessibility-aware)- **`findBy*` for async elements** — not `waitFor` + `getBy*`- **`userEvent` over `fireEvent`** — more realistic interaction simulation- **`queryBy*` only for non-existence assertions** (`.not.toBeOnTheScreen()`)- **v14: always `await`** every API (including `render`, `fireEvent`, `act`)

Frequently asked questions

React Native Testing