jest

Run TypeScript unit tests with Jest by executing the provided helper script in a bash-compatible shell, passing coverage flags to generate reports. This requires Jest available locally or via npx/pnpx/yarn, and optional ts-jest or @swc/jest for transforms.

The best way to mock modules and update snapshots for JavaScript unit tests is using built-in Jest patterns for mocking, spies, and timer control. Run the helper script with snapshot update flags to maintain component snapshot tests.

Yes, this workflow supports Node.js backend service logic validation with isolated mocks. It applies to projects with jest in devDependencies or a package.json test script, enabling isolated mock testing for backend service logic.

Yes, you can use SWC transforms instead of ts-jest for TypeScript testing in CI scenarios. The environment supports optional ts-jest or @swc/jest transforms to handle TypeScript files during Jest test execution.

Jest unit tests may not be working if the project environment lacks a bash-compatible shell or local Jest availability via npx/pnpx/yarn. Ensure test files match common patterns and jest.config files are properly configured.

You need a project environment with Jest available locally or via npx/pnpx/yarn to run parameterized tests and filter test suites. A package.json test script for unit testing ensures discoverability, along with jest.config files.