Vitest "No test files found" - Fix Glob & Config in CI

By Daniel Zoghalchali·Latchkey

Vitest scanned for test files and found none that match its include pattern, so it exits non-zero. Usually the glob does not match your filenames, or CI runs from a directory where no tests live.

What this error means

Vitest prints "No test files found, exiting with code 1" and fails the job. Locally you may run a single file by name and see it pass, masking that the default glob matches nothing.

Vitest output

No test files found, exiting with code 1

  include: **/*.{test,spec}.?(c|m)[jt]s?(x)
  exclude: **/node_modules/**

Diagnose it: flake, environment, or genuine failure?

Before debugging the assertion, establish whether the test is deterministic. A test that fails only in CI is usually order-dependent, time-dependent, or racing something, and fixing the assertion will not help.

Terminal

# does it fail in isolation?
npx vitest run path/to/file.test.ts

# is it order dependent? run the suite in a random order twice
npx vitest run --sequence.shuffle

# is it a race? run the same file repeatedly
for i in $(seq 1 20); do npx vitest run path/to/file.test.ts || break; done

Common causes

Filenames do not match the include glob

Vitest only picks up *.test.*/*.spec.* by default. Files named *.tests.ts or under a non-default folder are ignored.

Wrong working directory or root in CI

If the job runs vitest from the repo root but tests live in a workspace package, the resolved root contains no matching files.

How to fix it

Set an include pattern that matches your files

vitest.config.ts

// vitest.config.ts
import { defineConfig } from 'vitest/config';
export default defineConfig({
  test: { include: ['src/**/*.{test,spec}.{ts,tsx}'] },
});

Run from the right directory

Confirm CI runs Vitest in the package that holds the tests (use --root or a working-directory).
For monorepos, define a Vitest workspace so each package’s tests are discovered.
Pass --dir or an explicit path to scope discovery if needed.

CI-only causes worth ruling out

Runners have fewer cores than a laptop, so timing-sensitive tests that pass locally fail under contention.
No TTY and a different locale or timezone. Snapshot tests containing formatted dates or numbers are the usual casualty; pin TZ and LANG in the job.
Parallel workers sharing a database, a port, or a temp directory. Give each worker its own namespace.
Default timeouts calibrated on a fast machine. A cold runner is slower on first execution, especially before any cache warms.

How to prevent it

Commit an explicit include glob instead of relying on defaults.
In monorepos, use a Vitest workspace config.
Add a smoke test so an empty run is obviously wrong.

Frequently asked questions

What causes Vitest "No test files found"?

There are 2 common causes: filenames do not match the include glob and wrong working directory or root in ci. Vitest only picks up *.test.*/*.spec.* by default.

How do I fix Vitest "No test files found"?

There are 2 fixes depending on which cause you have: set an include pattern that matches your files and run from the right directory. Work through them in order, since the first is the most common.

What does Vitest "No test files found" actually mean?

Vitest prints "No test files found, exiting with code 1" and fails the job.

How do I stop Vitest "No test files found" happening again?

Commit an explicit include glob instead of relying on defaults. The prevention section lists 3 changes that keep it from recurring.

References

GitHub Actions documentation