Search skills.../

Javascript Typescript Jest | Skills Pool

Skill File

Javascript Typescript Jest

Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns.

github30,320 starsFeb 24, 2026

Occupation
Categories: Testing

Skill Content

Test Structure

Name test files with .test.ts or .test.js suffix
Place test files next to the code they test or in a dedicated __tests__ directory
Use descriptive test names that explain the expected behavior
Use nested describe blocks to organize related tests
Follow the pattern: describe('Component/Function/Class', () => { it('should do something', () => {}) })

Effective Mocking

Mock external dependencies (APIs, databases, etc.) to isolate your tests
Use jest.mock() for module-level mocks
Use jest.spyOn() for specific function mocks
Use mockImplementation() or mockReturnValue() to define mock behavior
Reset mocks between tests with jest.resetAllMocks() in afterEach

Testing Async Code

Always return promises or use async/await syntax in tests

Related Skills

Quick Install

Javascript Typescript Jest

npx skills add github/awesome-copilot

Download Skill Open repository

Author: github
stars: 30,320
Updated: Feb 24, 2026
Occupation

On this page

01Test Structure

Use resolves/rejects matchers for promises

Set appropriate timeouts for slow tests with jest.setTimeout()

Snapshot Testing

Use snapshot tests for UI components or complex objects that change infrequently
Keep snapshots small and focused
Review snapshot changes carefully before committing

Testing React Components

Use React Testing Library over Enzyme for testing components
Test user behavior and component accessibility
Query elements by accessibility roles, labels, or text content
Use userEvent over fireEvent for more realistic user interactions

Common Jest Matchers

Basic: expect(value).toBe(expected), expect(value).toEqual(expected)
Truthiness: expect(value).toBeTruthy(), expect(value).toBeFalsy()
Numbers: expect(value).toBeGreaterThan(3), expect(value).toBeLessThanOrEqual(3)
Strings: expect(value).toMatch(/pattern/), expect(value).toContain('substring')
Arrays: expect(array).toContain(item), expect(array).toHaveLength(3)
Objects: expect(object).toHaveProperty('key', value)
Exceptions: expect(fn).toThrow(), expect(fn).toThrow(Error)
Mock functions: expect(mockFn).toHaveBeenCalled(), expect(mockFn).toHaveBeenCalledWith(arg1, arg2)

02

Effective Mocking

03Testing Async Code

04Snapshot Testing

05Testing React Components

06Common Jest Matchers

Software Quality Assurance Analysts and Testers

Test

Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.

Feature Flags

Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.

Unit Tests

Use when running unit tests in the VS Code repo. Covers the runTests tool, scripts/test.sh (macOS/Linux) and scripts/test.bat (Windows), and their supported arguments for filtering, globbing, and debugging tests.

microsoft184.0k

Integration Tests

Use when running integration tests in the VS Code repo. Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.

microsoft184.0k

Write Frontend Tests

Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them. TRIGGER when user asks to write frontend tests, add test coverage, or 'write tests for my changes'.

Significant-Gravitas183.5k

Golang Testing

テスト駆動開発とGoコードの高品質を保証するための包括的なテスト戦略。

Software Quality Assurance Analysts and Testers