
javascript-typescript-jest
✓ Official★ 36,200by github · part of github/awesome-copilot
Jest testing best practices for JavaScript and TypeScript projects with mocking, async handling, and React patterns. Organize tests with descriptive names in nested describe blocks, using .test.ts / .test.js files placed alongside source code or in __tests__ directories Mock external dependencies with jest.mock() , jest.spyOn() , and mockImplementation() , resetting between tests to prevent state leakage Handle async code with promises, async/await , and resolves / rejects matchers; set...
Jest testing best practices for JavaScript and TypeScript projects with mocking, async handling, and React patterns. Organize tests with descriptive names in nested describe blocks, using .test.ts / .test.js files placed alongside source code or in __tests__ directories Mock external dependencies with jest.mock() , jest.spyOn() , and mockImplementation() , resetting between tests to prevent state leakage Handle async code with promises, async/await , and resolves / rejects matchers; set...
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
by github
Jest testing best practices for JavaScript and TypeScript projects with mocking, async handling, and React patterns. Organize tests with descriptive names in nested describe blocks, using .test.ts / .test.js files placed alongside source code or in tests directories Mock external dependencies with jest.mock() , jest.spyOn() , and mockImplementation() , resetting between tests to prevent state leakage Handle async code with promises, async/await , and resolves / rejects matchers; set...
npx skills add https://github.com/github/awesome-copilot --skill javascript-typescript-jest
Download ZIPGitHub36.2k
Test Structure
-
Name test files with
.test.tsor.test.jssuffix -
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()ormockReturnValue()to define mock behavior -
Reset mocks between tests with
jest.resetAllMocks()inafterEach
Testing Async Code
-
Always return promises or use async/await syntax in tests
-
Use
resolves/rejectsmatchers 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
userEventoverfireEventfor 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)
npx skills add https://github.com/github/awesome-copilot --skill javascript-typescript-jestRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.