javascript-typescript-jest

What problem does it solve? Writing consistent, well-structured Jest tests is hard when teams lack shared conventions for test organization, mocking, async handling, and assertions, leading to flaky and hard-to-maintain test suites. ## Core Features & Use Cases - Test Structure Conventions: Enforces naming patterns, describe/it organization, and descriptive test names for readable suites. - Mocking Strategies: Covers jest.mock(), jest.spyOn(), mock implementations, and mock reset patterns to isolate units under test. - Async, Snapshot, and React Testing: Provides guidance on promises, snapshot testing, and React Testing Library practices including userEvent over fireEvent. - Use Case: When adding tests to a TypeScript service that calls an external API, apply the mocking guidance to stub the API layer and use the matcher reference to write precise assertions. ## Quick Start Write Jest tests for my TypeScript utility module following best practices for structure, mocking, and assertions.