Configuration file equivalent for --passWithNoTests flag

[astorije]

🚀 Feature Proposal

Add a passWithNoTests boolean support in the configuration file, to have the same effect as the --passWithNoTests CLI flag.

Motivation

We currently use a shared configuration file across our organization, so that every repo running Jest will have the same default configuration (we do the same for Prettier, TSLint, Webpack, etc.). This ensures consistency, avoids surprises, and lets our teams have a sort of internal "zero conf" set up with the preferences/settings of the engineering organization.

This works really well with Jest, except we are now adding --passWithNoTests to all our new repos, where a configuration file equivalent would let us do it once.

Example

In jest.config.js (if using the JS format):

module.exports = {
  preset: 'ts-jest',
  moduleFileExtensions: ['ts', 'tsx', 'js'],
  globals: { 'ts-jest': { tsConfig: 'tsconfig.json' } },
  testMatch: ['**/test/**/*.test.(ts|tsx)'],
  // ...
  passWithNoTests: true,
};

[Mark1626]

@SimenB I can pick this up, if this feature is needed

[celiamarshall]

Will this be added? @M4rk9696 Thanks!

[eladchen]

So... That is not going to happen?

[risen228]

Any progress?

[bluelovers]

need this

[pisharodySrikanth]

+1

[theomessin]

+1

[sagiBarkol]

+1

[ronaldndirangu]

+1

[humoyun91]

+1

[noahvarghese]

+1

[mattsears18]

+1

[Mikuu]

+1

[fguitton]

Isn't this something which was addressed in Jest 22 in #4639 ?
You can even read:

This is a weird requirement to get CLI flags to pass through
Originally posted by @SimenB in #4639 (comment)

A quick test in Jest 27 just now seems to show this working properly.
This is via config file, CLI single --config argument, or separate arguments:

$> jest --version
27.4.7

$> jest
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In \repos\project
  14 files checked.
  testMatch: ['**/__tests__/**/*.[jt]s?(x)', '**/?(*.)+(spec|test).[tj]s?(x)'] - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 14 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches


$> jest --config='{\"testMatch\":[\"*.js\"]}'
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In \repos\project
  14 files checked.
  testMatch: *.js - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 14 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches


$> jest --config='{\"testMatch\":[\"*.js\"]}' --passWithNoTests
No tests found, exiting with code 0

$> jest --config='{\"testMatch\":[\"*.js\"],\"passWithNoTests\":true}'
No tests found, exiting with code 0

$> echo '{"testMatch": ["*.js"],"passWithNoTests": true}' > jest.config.json && jest
No tests found, exiting with code 0

$> echo '{"testMatch": ["*.js"]}' > jest.config.json && jest
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In \repos\project
  14 files checked.
  testMatch: *.js - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 14 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches

Am I missing something ?

[mikemaccana]

Quoting:

$> jest --config='{\"testMatch\":[\"*.js\"],\"passWithNoTests\":true}'
No tests found, exiting with code 0

Hrm odd, actually using a config file with passWithNoTests: true, fails with:

 FAIL  src/index.test.ts
  ● Test suite failed to run

    Your test suite must contain at least one test.

$ npx jest --version
27.5.1

[LeonardoRick]

Needing this too!

[kafir-coder]

Really needing this too!!!

@Mark1626 any news?

[FrameMuse]

I mean, I don't know, but I've just tested it and it's working.

Before

After

[moegelin]

Works for me as well (29.4.3). It seems it was just forgotten to add to the documentation.

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[tmtron]

+1