Write Jest tests using TDD patterns and factory functions

Testing Patterns and Utilities is a guide to Jest-based unit testing, particularly for React Native components. It combines a red-green-refactor workflow with behavior-focused assertions, reusable props and data factories, provider-aware rendering, and organized test cases. The goal is to make tests express public behavior and business requirements rather than mirror implementation details.

The TDD sequence starts with a failing test, adds minimal production code to pass it, and refactors after green. It also advocates descriptive names and one behavior per test. These are workflow conventions to apply within the actual repository's test setup, not evidence that any supplied sample has been executed.

Use it when writing component tests, building consistent test fixtures, or structuring a regression test around observable behavior. It is relevant to rendering, loading and empty states, user interactions, asynchronous results, and edge cases.

Do not treat a called mock as sufficient proof that the user-visible behavior works. The source explicitly contrasts mock-call assertions with checking rendered results. Its examples include module and generated GraphQL-hook mocks, so the actual project's rules and boundaries still determine where those patterns are appropriate. They do not validate a real network service or database.

Inputs include a component or public API, the expected behavior, provider requirements, fixture types, and the installed test environment. Outputs are focused Jest tests, custom render helpers, and factory functions with sensible defaults and explicit overrides. The sample getMockX pattern uses Partial types so an individual test changes only the fields relevant to its case.

A custom render wrapper supplies required context such as a theme provider. Component-prop factories include callback spies and default loading values; data factories keep required fields consistent. The source organizes describe blocks around rendering, interactions, and edge cases, clearing mocks before each test.

Query guidance distinguishes elements that must exist, elements expected to be absent, and asynchronous appearance. Interaction examples change form fields, press a button, and wait for a submit callback. Adapt asynchronous assertions to the installed library's semantics and await actual results rather than assuming a truthy promise proves rendering.

The examples use Jest, TypeScript, React, and @testing-library/react-native. Related UI-pattern guidance covers loading, error, empty, and success states, while debugging guidance calls for a test that reproduces a defect before the fix. Run the full suite with:

npm test

It also lists coverage and single-file commands, which depend on the project's package scripts. Module paths, generated hooks, theme providers, and sample components are application-specific rather than bundled assets.

This guide supports developers maintaining React Native component tests who need consistent fixtures, clear behavior assertions, and a repeatable test-first workflow.