react-native-testing
Write tests using React Native Testing Library (RNTL) v13 and v14 (`@testing-library/react-native`). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React 18, sync render) and v14 (React 19+, async render). Triggers on: test files for React Native components, RNTL imports, mentions of "testing library", "write tests", "component tests", or "RNTL".
98
100%
Does it follow best practices?
Impact
94%
1.70xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
18%Payment Form Testing
RNTL v14 async API patterns
Await render
100%
100%
Await fireEvent
100%
100%
screen for queries
100%
100%
getByRole as primary query
0%
100%
userEvent over fireEvent
100%
100%
Fake timers with userEvent
0%
100%
RNTL matchers used
100%
100%
No removed v14 APIs
100%
100%
No act() wrapping
100%
100%
No manual cleanup
100%
100%
100%
47%News Feed Component Tests
Query selection and async element patterns
screen for queries
100%
100%
getByRole priority
0%
100%
queryBy* for non-existence only
70%
100%
findBy* for async elements
100%
100%
No side effects in waitFor
100%
100%
One assertion per waitFor
100%
100%
userEvent over fireEvent
0%
100%
Fake timers with userEvent
0%
100%
within() for list items
0%
100%
No act() wrapping
100%
100%
toBeOnTheScreen matcher
0%
100%
84%
52%Settings Screen Tests
ARIA props, RNTL matchers, and context providers
getByRole state options
0%
0%
getByRole with options
100%
100%
No raw prop assertions
40%
100%
RNTL state matchers
0%
100%
wrapper option for providers
0%
100%
screen for queries
100%
100%
queryBy* for non-existence only
50%
100%
toBeOnTheScreen over toBeNull checks
0%
100%
No manual cleanup
100%
100%
userEvent for interactions
0%
60%
Fake timers with userEvent
0%
100%
- Repository
- callstack/react-native-testing-library
- Commit
2923d11
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.