First green test
Create a sum(a, b) function and a Jest test file with 3 cases (positive, zero, negative). Run in watch mode and fix failures.
DevOps & Tooling / Knowledge library
Jest
javascript test runner with mocks and coverage
Why learn Jest?
Jest gives teams a fast, standard way to run automated tests, mock dependencies, and measure coverage. It reduces regressions, shortens feedback loops, and plugs directly into CI/CD gates so broken code is blocked before deploy.
Where it came from
2014: Created at Facebook to test React code with minimal setup. 2016: Open-sourced and quickly adopted beyond React projects. Jest 27: jest-circus became the default test runner. Jest 28+: package split and cleanup improved install footprint and maintenance. Recent majors focus on stability, ESM workflows, and CI performance.
- 2014: Created at Facebook to test React code with minimal setup.
- 2016: Open-sourced and quickly adopted beyond React projects.
- Jest 27: jest-circus became the default test runner.
- Jest 28+: package split and cleanup improved install footprint and maintenance.
- Recent majors focus on stability, ESM workflows, and CI performance.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Create a sum(a, b) function and a Jest test file with 3 cases (positive, zero, negative). Run in watch mode and fix failures.
- Test a service function that calls fetch. Mock fetch, assert called URL, and assert transformed JSON output.
- Add Jest coverage thresholds to a project and wire them into CI so pull requests fail when lines coverage drops below 80%.
- Given an unstable async test, replace arbitrary timeouts with proper async/await and deterministic mocks.
- Configure Jest in a monorepo to run only changed package tests locally while full tests run in CI.
More ways to practice
Mock an API call
Test a service function that calls fetch. Mock fetch, assert called URL, and assert transformed JSON output.
CI quality gate
Add Jest coverage thresholds to a project and wire them into CI so pull requests fail when lines coverage drops below 80%.
Refactor flaky async test
Given an unstable async test, replace arbitrary timeouts with proper async/await and deterministic mocks.
Monorepo selective testing
Configure Jest in a monorepo to run only changed package tests locally while full tests run in CI.
Documentation and sources
- Official docs (jestjs.io)
- CLI options (jestjs.io)
- Mock functions (jestjs.io)
- Configuration (jestjs.io)
Catalog research notes
- Aligns with current Node LTS releases; older Node versions are regularly removed.
- ESM interoperability keeps improving for mixed CommonJS/ESM repositories.
- Watch mode, filtering flags, and caching continue to reduce local feedback time.
- Reporter and CLI output refinements improve CI debugging speed.
Connect the ideas
Explore next
Real World Example
Automating Financial Calculation Validation
A fintech startup building a microservices-based interest calculation engine.
The business problem
Manual verification of interest logic is slow and error-prone, leading to inconsistent financial reporting across services.
How this topic solves it
Implementing Jest as a centralized test runner allows developers to define deterministic unit tests for core calculation functions, ensuring consistent output before deployment.
- Install Jest as a development dependency using npm or yarn.
- Define core logic in a standalone module, such as interestCalculator.js.
- Create a corresponding test file, interestCalculator.test.js, using the test() and expect() functions.
- Update the package.json scripts section to include a test command that invokes the Jest runner.
- Execute the test suite via the command line to validate logic against expected outcomes.
The flow from source code to validation.
interestCalculator.js
interestCalculator.test.js
CLI execution engine
Pass/Fail output
- Source Code → imported by → Test Suite
- Test Suite → processed by → Jest Runner
- Jest Runner → outputs → Test Results
Implementation example
This code demonstrates the core Jest pattern: importing a function and using expect with a matcher (toBe) to verify the output.
const calculateInterest = require('./interestCalculator');
// Validate interest logic against known inputs
test('calculates 5% interest on 100 to equal 5', () => {
expect(calculateInterest(100, 0.05)).toBe(5);
});Expected business outcome
Developers gain immediate feedback on logic changes, significantly reducing the risk of regressions in financial calculations.
Limitations and checks
Jest does not perform type-checking when using Babel for TypeScript transpilation; developers must run the TypeScript compiler separately to ensure type safety.