<< All versions
Skill v1.0.1
currentAutomated scan100/100sickn33/agentic-awesome-skills/testing-patterns
+4 new
──Details
PublishedOctober 26, 2026 at 10:30 AM
Content Hashsha256:b51a8e25ee4baefb...
Git SHAd38c29b8765d
Bump Typepatch
──Files
Files (1 file, 6.3 KB)
SKILL.md6.3 KBactive
SKILL.md · 271 lines · 6.3 KB
version: "1.0.1" name: testing-patterns description: "Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle." risk: critical source: community date_added: "2026-02-27"
Testing Patterns and Utilities
Testing Philosophy
Test-Driven Development (TDD):
- Write failing test FIRST
- Implement minimal code to pass
- Refactor after green
- Never write production code without a failing test
Behavior-Driven Testing:
- Test behavior, not implementation
- Focus on public APIs and business requirements
- Avoid testing implementation details
- Use descriptive test names that describe behavior
Factory Pattern:
- Create
getMockX(overrides?: Partial<X>)functions - Provide sensible defaults
- Allow overriding specific properties
- Keep tests DRY and maintainable
Test Utilities
Custom Render Function
Create a custom render that wraps components with required providers:
typescript
// src/utils/testUtils.tsximport { render } from '@testing-library/react-native';import { ThemeProvider } from './theme';export const renderWithTheme = (ui: React.ReactElement) => {return render(<ThemeProvider>{ui}</ThemeProvider>);};
Usage:
typescript
import { renderWithTheme } from 'utils/testUtils';import { screen } from '@testing-library/react-native';it('should render component', () => {renderWithTheme(<MyComponent />);expect(screen.getByText('Hello')).toBeTruthy();});
Factory Pattern
Component Props Factory
typescript
import { ComponentProps } from 'react';const getMockMyComponentProps = (overrides?: Partial<ComponentProps<typeof MyComponent>>) => {return {title: 'Default Title',count: 0,onPress: jest.fn(),isLoading: false,...overrides,};};// Usage in testsit('should render with custom title', () => {const props = getMockMyComponentProps({ title: 'Custom Title' });renderWithTheme(<MyComponent {...props} />);expect(screen.getByText('Custom Title')).toBeTruthy();});
Data Factory
typescript
interface User {id: string;name: string;email: string;role: 'admin' | 'user';}const getMockUser = (overrides?: Partial<User>): User => {return {id: '123',name: 'John Doe',email: 'john@example.com',role: 'user',...overrides,};};// Usageit('should display admin badge for admin users', () => {const user = getMockUser({ role: 'admin' });renderWithTheme(<UserCard user={user} />);expect(screen.getByText('Admin')).toBeTruthy();});
Mocking Patterns
Mocking Modules
typescript
// Mock entire modulejest.mock('utils/analytics');// Mock with factory functionjest.mock('utils/analytics', () => ({Analytics: {logEvent: jest.fn(),},}));// Access mock in testconst mockLogEvent = jest.requireMock('utils/analytics').Analytics.logEvent;
Mocking GraphQL Hooks
typescript
jest.mock('./GetItems.generated', () => ({useGetItemsQuery: jest.fn(),}));const mockUseGetItemsQuery = jest.requireMock('./GetItems.generated').useGetItemsQuery as jest.Mock;// In testmockUseGetItemsQuery.mockReturnValue({data: { items: [] },loading: false,error: undefined,});
Test Structure
typescript
describe('ComponentName', () => {beforeEach(() => {jest.clearAllMocks();});describe('Rendering', () => {it.todo('should render component with default props');it.todo('should render loading state when loading');});describe('User interactions', () => {it.todo('should call onPress when button is clicked');});describe('Edge cases', () => {it.todo('should handle empty data gracefully');});});
Query Patterns
typescript
// Element must existexpect(screen.getByText('Hello')).toBeTruthy();// Element should not existexpect(screen.queryByText('Goodbye')).toBeNull();// Element appears asynchronously// async-appearance-example: await the element, not the Promiseexpect(await screen.findByText('Loaded')).toBeTruthy();
User Interaction Patterns
typescript
import { fireEvent, screen, waitFor } from '@testing-library/react-native';it('should submit form on button click', async () => {const onSubmit = jest.fn();renderWithTheme(<LoginForm onSubmit={onSubmit} />);fireEvent.changeText(screen.getByLabelText('Email'), 'user@example.com');fireEvent.changeText(screen.getByLabelText('Password'), 'password123');fireEvent.press(screen.getByTestId('login-button'));await waitFor(() => {expect(onSubmit).toHaveBeenCalled();});});
Anti-Patterns to Avoid
Testing Mock Behavior Instead of Real Behavior
typescript
// Bad - testing the mockexpect(mockFetchData).toHaveBeenCalled();// Good - testing actual behaviorexpect(screen.getByText('John Doe')).toBeTruthy();
Not Using Factories
typescript
// Bad - duplicated, inconsistent test datait('test 1', () => {const user = { id: '1', name: 'John', email: 'john@test.com', role: 'user' };});it('test 2', () => {const user = { id: '2', name: 'Jane', email: 'jane@test.com' }; // Missing role!});// Good - reusable factoryconst user = getMockUser({ name: 'Custom Name' });
Best Practices
- Always use factory functions for props and data
- Test behavior, not implementation
- Use descriptive test names
- Organize with describe blocks
- Clear mocks between tests
- Keep tests focused - one behavior per test
Running Tests
bash
# Run all testsnpm test# Run with coveragenpm run test:coverage# Run specific filenpm test ComponentName.test.tsx
Integration with Other Skills
- react-ui-patterns: Test all UI states (loading, error, empty, success)
- systematic-debugging: Write test that reproduces bug before fixing
When to Use
Use when writing Jest unit tests, test factories and mocks, or diagnosing a failing test through a red-green-refactor cycle.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.