testMatch doesn't glob as expected

i’m setting up jest’s testMatch config, but it doesn’t glob as expected. my sanity-check command looks into the test folder relative to the project, goes to any depth, and selects any file that ends in .js:

ls ./test/**/*.js | wc -l

running that returns 92. which makes sense, i have 92 files in that directory structure (some tests and some test utils). but when i run jest with the same glob it says there are no tests found:

yarn run v1.9.4
$ jest --config jest.config.json
No tests found
In /Users/<user>/<repo>
  460 files checked.
  testMatch: ./test/**/*.js - 0 matches
  testPathIgnorePatterns: /node_modules/ - 460 matches
Pattern:  - 0 matches
error Command failed with exit code 1.

is this an issue with jest? with micromatch?

[lohfu]

I too have problems with the testMatch globbing.

Changing the built in:

testMatch: [
  "**/__tests__/**/*.[jt]s?(x)",
  "**/?(*.)+(spec|test).[tj]s?(x)"
],

to

testMatch: [
  "src/**/__tests__/**/*.[jt]s?(x)",
  "src/**/?(*.)+(spec|test).[tj]s?(x)"
],

will cause no files to be matches. To resolve this i have to:

testMatch: [
  path.join(__dirname, 'src/**/__tests__/**/*.[jt]s?(x)'),
  path.join(__dirname, 'src/**/?(*.)+(spec|test).[tj]s?(x)'),
],

[rickhanlonii]

Thanks!

We can look into why those globs don’t work - just wanted to verify that it’s the relative pathing