[Bug]: Jest 30 testPathPatterns not working in Jest config file

[lencioni]

Version

30.0.0-beta.5

Steps to reproduce

1. clone https://github.com/lencioni/jest-test-path-patterns.git
2. yarn install
3. yarn jest --config singular.config.js
4. yarn jest --config plural.config.js

Expected behavior

I expect to see no configuration validation warnings for the plural config, and I expect the plural config to not try to run the helper file as a test.

Actual behavior

The singular config with testPathPattern logs this warning:

● Deprecation Warning:

  Option "testPathPattern" was replaced by "testPathPatterns".

  Please update your configuration.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

● Deprecation Warning:

  Option "testPathPattern" was replaced by "testPathPatterns".

  Please update your configuration.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

The plural config with testPathPatterns logs this warning:

● Validation Warning:

  Unknown option "testPathPatterns" with value [/\.test\.js$/] was found.
  This is probably a typing mistake. Fixing it will remove this message.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

● Validation Warning:

  Unknown option "testPathPatterns" with value [/\.test\.js$/] was found.
  This is probably a typing mistake. Fixing it will remove this message.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

Both the plural and the singular configs run the helper file.

The --testPathPatterns CLI flag works without any validation warnings and it does not run the helper file:

yarn jest --testPathPatterns=".*\.test\.js$"

Additional context

Possibly related:

• [Docs]: jest30 testRegex, testPathPatterns breaking #15630

Environment

System:
    OS: macOS 15.4.1
    CPU: (8) arm64 Apple M3
  Binaries:
    Node: 22.16.0 - ~/.local/share/mise/installs/node/22.16.0/bin/node
    Yarn: 1.22.22 - ~/.local/share/mise/installs/yarn/1.22.22/bin/yarn
    npm: 10.9.2 - ~/.local/share/mise/installs/node/22.16.0/bin/npm
  npmPackages:
    jest: ^30.0.0-beta.5 => 30.0.0-beta.5

[cpojer]

This should be fixed in jest@30.0.0-beta.8 hopefully.

[lencioni]

Sadly, I still see this with beta 8 @cpojer.

I updated the repo linked in the issue to beta 8.

[lencioni]

I was looking into this and discovered that testPathPattern in Jest 29 is not supported in the config file, it is only a CLI flag. Jest 29 logs this warning instead:

● Validation Warning:

  Unknown option "testPathPattern" with value /__tests__\/.*\.test\.js$/ was found.
  This is probably a typing mistake. Fixing it will remove this message.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

● Validation Warning:

  Unknown option "testPathPattern" with value /__tests__\/.*\.test\.js$/ was found.
  This is probably a typing mistake. Fixing it will remove this message.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

So I think this is more just an issue with the validation warning being confusing for this option in Jest 30, since it will show the deprecation warning instead of the unknown option warning when it is used in the Jest config.

[lencioni]

The upgrade guide needs a tweak. I'll open a PR for that now.

[gustav0d]

true, If you use testRegex instead it works perfectly on jest config

[cpojer]

Ah, so the issue is that it recommended you to use the other "option", then said that option didn't exist, because it's only a CLI flag?

If so, we should either fix the warning or just make it work as a config option too. What do you think?

[lencioni]

Yes, exactly. Either path seems good to me. I am not using this option, and I haven't thought deeply about whether it makes sense in config. But I guess I'm always a little surprised when there is a CLI flag that's not supported by config so that's probably the best resolution in the long run. But maybe it is easier to fix the warning and get this release out the door.