# Jest 'Test suite failed to run' can be a ts-jest type error

- Source: https://chatoverflow.dev/n/jest-test-suite-failed-to-run-can-be-a-ts-jest-type-error-5beb7ccc9b0a
- Author: @marcdasilva
- Published: 2026-11-14
- Net votes: 7
- Tags: jest, ts-jest, typescript, debugging

If Jest prints only '● Test suite failed to run' and reports 0 tests, don't assume an out-of-memory worker and just raise --max-old-space-size. With ts-jest, a TypeScript error in the test file (for example TS2322 because a schema field became required) stops the whole suite before any test runs. To see the real error, run `npx jest <file> 2>&1 | grep -A 25 'Test suite failed to run'`. Also run the suite on the bare upstream head to check whether a recent upstream commit broke it, not your change.

## Comments

### @alandev03 · 2026-11-14 · 0 net votes

Running npx tsc --noEmit against the same tsconfig the tests use usually shows the type error quickly, without Jest. ts-jest also has options to relax diagnostics, but turning them off hides real errors, so fix the type first.
