react-native-testing-patterns
Implements testing strategies for React Native components, MST stores, and services using Jest, React Testing Library, and Maestro. Use when writing unit, integration, or E2E tests in Purrsuit Mobile App.
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for implementing robust testing strategies in React Native applications. It integrates industry-standard tools like Jest, React Testing Library, and Maestro to facilitate unit, integration, and end-to-end (E2E) testing, ensuring high code quality and reliable mobile app performance.
Use Cases
- Unit testing MobX-State-Tree (MST) models to verify state transitions, actions, and data integrity.
- Creating component-level tests using React Testing Library to ensure UI elements render correctly and handle user interactions as expected.
- Implementing automated E2E testing flows with Maestro to validate critical user journeys and cross-screen navigation.
- Mocking Expo modules and native dependencies to create isolated, predictable, and fast-running test environments.
- Testing complex business logic within services and utility functions to prevent regressions during feature updates.
| name | react-native-testing-patterns |
|---|---|
| description | Implements testing strategies for React Native components, MST stores, and services using Jest, React Testing Library, and Maestro. Use when writing unit, integration, or E2E tests in Purrsuit Mobile App. |
React Native Testing Patterns
This skill provides the established testing patterns for the Purrsuit Mobile App, ensuring high code quality and reliable automated verification.
When to Use This Skill
Use this skill when you need to:
- Write unit tests for MST models and stores
- Create component tests using React Testing Library (RTL)
- Mock Expo modules or native dependencies
- Implement E2E flows using Maestro
- Test services, utility functions, or API logic
Unit Testing (MST)
Model Testing
import { MyModel } from "@/models/MyModel"
describe("MyModel", () => {
it("can be created", () => {
const instance = MyModel.create({ id: "1", name: "Test" })
expect(instance.name).toBe("Test")
})
it("handles actions correctly", () => {
const instance = MyModel.create({ id: "1", name: "Test" })
instance.setName("Updated")
expect(instance.name).toBe("Updated")
})
})
Component Testing (RTL)
Basic Component Render
import { render } from "@testing-library/react-native"
import { ThemeProvider } from "@/theme/context"
import { MyComponent } from "./MyComponent"
describe("MyComponent", () => {
it("renders correctly", () => {
const { getByText } = render(
<ThemeProvider>
<MyComponent text="Hello" />
</ThemeProvider>
)
expect(getByText("Hello")).toBeDefined()
})
})
Mocking Patterns
Mocking Expo Modules
Mocks are usually centralized in test/setup.ts.
jest.mock("expo-localization", () => ({
getLocales: () => [{ languageTag: "en-US", textDirection: "ltr" }],
}))
E2E Testing (Maestro)
Basic Flow Pattern
appId: ${MAESTRO_APP_ID}
onFlowStart:
- runFlow: ../shared/_OnFlowStart.yaml
---
- tapOn: "Home"
- assertVisible: "My Collection"
References
See MST_TESTING.md for detailed store testing patterns.
See COMPONENT_TESTING.md for RTL and theme provider patterns.
See MAESTRO_FLOWS.md for E2E testing best practices.