testing-jest
Apply when writing unit tests with Jest: assertions, mocking, async tests, and test organization.
When & Why to Use This Skill
This Claude skill provides comprehensive guidance and optimized code patterns for writing robust unit tests using the Jest framework. It empowers developers to implement high-quality testing suites by covering essential practices such as advanced assertions, function and module mocking, asynchronous test handling, and efficient test organization to ensure code reliability and maintainability.
Use Cases
- Writing structured unit tests for JavaScript or TypeScript logic using descriptive blocks and matchers.
- Mocking external dependencies, APIs, or modules to isolate the code under test and simulate various edge cases.
- Testing asynchronous functions and promises using modern async/await patterns or Jest's built-in resolves/rejects matchers.
- Implementing snapshot testing to detect unexpected UI or data structure changes over time.
- Managing test lifecycles with setup and teardown hooks (beforeEach, afterAll) to ensure test isolation and clean state.
| name | testing-jest |
|---|---|
| description | Apply when writing unit tests with Jest: assertions, mocking, async tests, and test organization. |
| version | 1.0.0 |
| tokens | ~650 |
| confidence | high |
| - https | //jestjs.io/docs/mock-functions |
| last_validated | 2025-01-10 |
| next_review | 2025-01-24 |
| tags | [testing, jest, unit-tests, mocking] |
When to Use
Apply when writing unit tests with Jest: assertions, mocking, async tests, and test organization.
Patterns
Pattern 1: Basic Test Structure
// Source: https://jestjs.io/docs/getting-started
describe('Calculator', () => {
describe('add', () => {
it('should add two positive numbers', () => {
expect(add(2, 3)).toBe(5);
});
it('should handle negative numbers', () => {
expect(add(-1, 5)).toBe(4);
});
});
});
Pattern 2: Common Matchers
// Source: https://jestjs.io/docs/expect
// Equality
expect(value).toBe(5); // Strict ===
expect(obj).toEqual({ a: 1 }); // Deep equality
expect(value).toBeNull();
expect(value).toBeDefined();
// Truthiness
expect(value).toBeTruthy();
expect(value).toBeFalsy();
// Numbers
expect(value).toBeGreaterThan(3);
expect(value).toBeCloseTo(0.3, 5); // Floating point
// Strings
expect(str).toMatch(/pattern/);
// Arrays/Objects
expect(array).toContain('item');
expect(obj).toHaveProperty('key', 'value');
// Errors
expect(() => fn()).toThrow('error message');
expect(() => fn()).toThrow(CustomError);
Pattern 3: Mocking Functions
// Source: https://jestjs.io/docs/mock-functions
// Mock function
const mockFn = jest.fn();
mockFn.mockReturnValue(42);
mockFn.mockResolvedValue({ data: [] }); // Async
// Verify calls
expect(mockFn).toHaveBeenCalled();
expect(mockFn).toHaveBeenCalledWith('arg1', 'arg2');
expect(mockFn).toHaveBeenCalledTimes(2);
// Mock module
jest.mock('./api', () => ({
fetchUser: jest.fn().mockResolvedValue({ id: '1', name: 'Test' }),
}));
Pattern 4: Async Tests
// Source: https://jestjs.io/docs/asynchronous
// Async/await (preferred)
it('should fetch data', async () => {
const data = await fetchData();
expect(data).toEqual({ id: 1 });
});
// Resolves/Rejects
it('should resolve with data', async () => {
await expect(fetchData()).resolves.toEqual({ id: 1 });
});
it('should reject with error', async () => {
await expect(failingFn()).rejects.toThrow('Network error');
});
Pattern 5: Setup and Teardown
// Source: https://jestjs.io/docs/setup-teardown
describe('Database tests', () => {
let db: Database;
beforeAll(async () => {
db = await createTestDatabase();
});
afterAll(async () => {
await db.close();
});
beforeEach(async () => {
await db.clear();
});
it('should insert record', async () => {
await db.insert({ id: 1 });
expect(await db.count()).toBe(1);
});
});
Pattern 6: Snapshot Testing
// Source: https://jestjs.io/docs/snapshot-testing
it('should match snapshot', () => {
const component = render(<Button>Click</Button>);
expect(component).toMatchSnapshot();
});
// Inline snapshot
expect(format(date)).toMatchInlineSnapshot(`"2025-01-10"`);
Anti-Patterns
- Testing implementation - Test behavior, not internal details
- Shared mutable state - Reset in beforeEach
- No assertion - Every test needs expect()
- Over-mocking - Test real code when possible
Verification Checklist
- Tests isolated (no shared state)
- Mocks reset between tests
- Async tests properly awaited
- Descriptive test names
- Arrange-Act-Assert pattern