testing-patterns

Create a getMockX function that returns default values and spreads an optional overrides parameter, such as getMockUser({ role: 'admin' }). This keeps test data DRY and consistent across all tests while allowing per-test customization.

Use jest.mock on the generated hooks file with a factory returning jest.fn() for the hook, then access it via jest.requireMock. Set return values per test with mockReturnValue to control data, loading, and error states.

TDD means writing a failing test first, implementing the minimal code to make it pass, then refactoring while tests stay green. Never write production code without a failing test driving it.

Yes, the patterns use @testing-library/react-native with a custom render function that wraps components in required providers like ThemeProvider. Queries use screen.getByText, queryByText, and fireEvent for interactions.

Asserting that a mock was called only verifies the mock, not real behavior. Instead, assert on observable outcomes like rendered text or state changes, which keeps tests resilient to implementation refactors.