react-native-testing

Fix flaky React Native component tests by standardizing screen-based queries, preferring async userEvent over fireEvent, and applying correct waitFor rules to avoid race conditions. This approach ensures deterministic UI interactions and stable async waiting across RNTL versions.

The correct query priority for React Native Testing Library components uses getByRole and related accessibility queries first. This strategy targets the right UI elements reliably, avoiding brittle prop checks and ensuring components are tested as users perceive them.

You should use async userEvent over fireEvent for React Native component interactions. userEvent provides more realistic interaction simulation and works with findBy* and correct waitFor rules to prevent race conditions during async render and event testing.

Yes, React Native Testing Library v14 enforces version-specific async render and event rules. You must apply version-aware guidance to choose correct render semantics, query priority, and avoid removed APIs and legacy accessibility props when upgrading.

Common waitFor anti-patterns in Jest React Native testing include causing side effects inside waitFor, unnecessary act() wrapping, and destructuring render queries. Avoid these alongside manual cleanup and legacy accessibility props to maintain fast, reliable tests.