No matching test files found in Vitest file resolver

Answer

Set passWithNoTests: true in the test section of your Vitest configuration. When the include/exclude resolver matches no files, Vitest prints a “No test files found” message and exits with code 0. Real assertion failures and runtime errors still exit non-zero, so CI alerts stay meaningful.

Confirmed behavior

• Vitest resolves test files from test.include and test.exclude patterns.
• passWithNoTests: true changes a zero-match result to exit code 0.
• This option does not mask failing tests, missing setup files, or unhandled errors.

Steps

1. Open vitest.config.ts or vitest.config.js.
2. Add passWithNoTests: true inside test:

import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    include: ['src/**/*.test.{js,ts,mjs}'],
    exclude: ['node_modules/**', 'dist/**', 'build/**'],
    passWithNoTests: true,
  },
});

3. Run npx vitest run where no test files match the patterns.
4. Verify the exit code: npx vitest run; echo "exit=$?" should print exit=0.
5. Optionally add a temporary failing assertion to confirm real failures still exit non-zero, then remove it.

If the option is missing

Run npx vitest --version. If your installed Vitest does not support passWithNoTests, upgrade Vitest or add a no-op placeholder test file that matches your include pattern. Avoid vitest run || true as a general fix because it hides genuine failures.

Missing diagnostic

Could you share your Vitest version? It determines whether passWithNoTests is available or whether an upgrade or workaround is needed.