jest: jest cannot find tests when projects are defined in configuration

After searching a while I found out that if you use:

{
    roots: ["<rootDir>/src/", "<rootDir>/__tests__/"],
}

but don’t have one of those folders everything else is ignored too.

In my case jest checks recursively but still doesn’t find any test files. The only difference between your and my config is that I use <rootDir> in the testMatch option

 testMatch: [
    "<rootDir>/src/**/?(*.)(itest).{js,jsx,mjs}"
  ],

Deleting it doesn’t change anything.

Maybe it’s somehow connected with #6546

When I run test with jest I get an error that no test is found both my tests and js files are inside the static folder

Here is my package json

{
  "name": "static",
  "version": "1.0.0",
  "description": "",
  "main": "main.js",
  "directories": {
    "test": "tests"
  },
  "scripts": {
    "test": "jest"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "jest": "^23.6.0"
  }
}

Error

No tests found
In /root/Desktop/Projects/iReporter/UI/static
  15 files checked.
  testMatch: **/__tests__/**/*.js?(x),**/?(*.)+(spec|test).js?(x) - 0 matches
  testPathIgnorePatterns: /node_modules/ - 15 matches
Pattern:  - 0 matches
npm ERR! Test failed.  See above for more details.

What could be the issue

“rootDir”: “./”,

Thanks !! I was quite frustrated with issue, and it resolved it quite nicely…

EDIT: I fixed it by adding a WORKDIR in my Dockerfile. Some other stuff in the root (added by codeship) seems to have interfered with Jest’s regex matching pattern somehow.

---

I got this issue, but only in CI (inside a docker container with NODE_ENV=test and --ci tag)

Using CRA with TS. No idea why its not finding the test. They are clearly there

@y4nnick I did manage to get this set up eventually. It was a royal pain though. My main Jest config looks like:

module.exports = {
  projects: [
    '<rootDir>/packages/api-service',
    '<rootDir>/packages/user-service',
    '<rootDir>/packages/web',
    '<rootDir>/packages/admin',
  ],
};

And within each package subdirectory I have a Jest config that looks more like:

module.exports = {
  "name": 'user-service',
  "displayName": 'user-service',
  "rootDir": './',
  "moduleFileExtensions": [
    "js",
    "json"
  ],
  "setupFilesAfterEnv": [
    "<rootDir>/__jest__/setup.js"
  ],
  "transform": {},
  "testRegex": "(/__tests__/.*|(\\.|/)(test))\\.js$",
  "coverageDirectory": "<rootDir>/../../coverage/user-service",
  "collectCoverageFrom": [
    "**/*.js"
  ],
  "coveragePathIgnorePatterns": [
    "/__jest__/",
    "jest.config.js"
  ]
};

I think it was the rootDir being different between top level and each package might have fooled me. Anyway, I got it working, more or less. npx jest works, as does npx jest --projects packages/xxxx. This was using Jest 24.1.0.

Yes, this is still an issue for me too. Right now, projects don’t seem to be useful. I can run a command like:

16:35:52 api-server$ npx jest --projects jest/projects/api-service.js 
No tests found
In /Users/stuart/git/api-server/jest/projects
  1 file checked.
  testMatch: /Users/stuart/git/api-server/__tests__/**/*.js - 0 matches
  testPathIgnorePatterns: /node_modules/ - 1 match
Pattern:  - 0 matches

When /Users/stuart/git/api-server/__tests__ definitely does contain a whole bunch of *.js files.

More documentation might help, but I’m sure there’s something else skewed too.

I have the same problem as you. All jest versions 23.0.0, 23.1.0, 23.20 don’t detect my tests.

{
  rootDir: path.join(__dirname, '../..'),
  testMatch: [..., path.join(__dirname, '../../**/?(*.)+(spec|test).[tj]s?(x)')],
}

This fixed it for me. Issue seems to be that the recursion is relative to the rootDir path.

Depends how nested your configuration file is, but basically you just need to set your root up as far as you need to go.

I suspect this might be a bug in how jest resolves the config file location, as least in mono repos where you have:

├── packages
│   ├── foo
│   │   ├── ...
│   │   └── package.json
│   ├── bar
│   │   ├── ...
│   │   └── package.json
│  └── baz
│       ├── ...
│       └── package.json
├── jest.config.js
└── package.json

Where the root jest.config.js contains projects configured using an object, and the individual packages use just jest as their test command (or jest --selectProjects foo for package foo). Running npm exec -- jest --showConfig from the packages/foo directory, the config ends up being the default configuration for jest, instead of what is in ../../jest.config.js

I added some tracing into https://github.com/facebook/jest/blob/main/packages/jest-config/src/resolveConfigPath.ts and found that it is trying to recurse up to the parent directories, but it fails to actually recurse upwards due to https://github.com/facebook/jest/blob/main/packages/jest-config/src/resolveConfigPath.ts#L60 not being the parent directory.

Before and after changing that line to path().dirname(absolutePath), with logs on the arguments of resolveConfigPath and resolveConfigPathByTraversing, I get the following:

Before:

 $ npm exec -- jest --showConfig

Trying: /<project>/packages/foo
cwd: /<project>/packages/foo

Trying: /<project>/packages/foo
cwd: /<project>/packages/foo
initial: /<project>/packages/foo, parent: /<project>/packages

Trying: /<project>/packages/foo
cwd: /<project>/packages/foo

Trying: /<project>/packages/foo
cwd: /<project>/packages/foo
initial: /<project>/packages/foo, parent: /<project>/packages

Found: /<project>/packages/foo/package.json

After:

$ npm exec -- jest --showConfig

Trying: /<project>/packages/foo
cwd: /<project>/packages/foo

Trying: /<project>/packages
cwd: /<project>/packages/foo
initial: /<project>/packages/foo, parent: /<project>

Trying: /<project>
cwd: /<project>/packages/foo
initial: /<project>/packages/foo, parent: /

Found: /<project>/jest.config.js

As you can see, in the before the directory it tries to load configuration from doesn’t change, despite attempting to recurse upwards. After the change, it correctly tries to load configuration from each of the parent directories.

Note: the package.json in /<project>/packages/foo/ does not include jest configuration (no jest key)

I’m going to try to write tests and a PR to fix the behaviour, though I’m not sure if this’ll break things at all.

Edit: clarified the found jest.config.js filename, in my project I’m using typescript, so had accidentally left the .ts extension, but it’s the same thing either way.

Any updates on this?

The problem is that it doesn’t recursively check all directories for tests in my project(s). Before it would check 62 files, but using this configuration it only checks 10 files. I’m unsure whether or not it’s even the root directory it’s checking or what else. There should really be some better configuration documentation for this library.

I ended up working around it by using 2 separate jest configs and one as base.

"scripts": {
	"test": "npm run test:node && npm run test:jsdom",
	"test:node": "jest --config=config/jest.node.config.js",
	"test:jsdom": "jest --config=config/jest.jsdom.config.js"
}

jest.base.config.js

const path = require('path');

module.exports = {
    rootDir: path.join(__dirname, '..'),
    verbose: true,
    moduleFileExtensions: [
        'js',
        'ts',
        'tsx',
        'json',
        'node',
    ],
    testPathIgnorePatterns: [
        '/node_modules/',
    ],
    collectCoverage: true,
    transform: {
        '^.+\\.tsx?$': 'ts-jest',
    },
};

jest.jsdom.config.js

const baseConfig = require('./jest.base.config');

module.exports = {
    ...baseConfig,
    testEnvironment: 'jsdom',
    testMatch: [
        '**/*.test.tsx'
    ],
    setupTestFrameworkScriptFile: './setupTests.ts',
};

jest.node.config.js

const baseConfig = require('./jest.base.config');

module.exports = {
    ...baseConfig,
    testEnvironment: 'node',
    testMatch: [
        '**/*.test.ts'
    ],
};

OFFT: Also the testRegex & testMatch properties aren’t getting resolved properly relatively to your rootDir aswell. So. Many. Errors.