Jest No Tests found

Question

running docker mhart/alpine-node:8 on macOS with

nodejs (6.10.3-r0) (18/18) yarn 0.24.6 jest 20.0.4

I have a __tests__/index.test.js file however, when running the code

node_modules/.bin/jest --watchAll I get the below output

No tests found
In /usr/src/app
5 files checked.
testMatch: /__tests__//*.js?(x),**/?(*.)(spec|test).js?(x) - 1 match
testPathIgnorePatterns: /node_modules/,/src,src - 0 matches
Pattern: "" - 0 matches

I've re-installed the package numbers times but to no avail.

The way I fixed this was by changing my docker-compose command slightly. I changed `command: npm run cover && bash — tamj0rd2, May 08 '20 at 18:46

score 21 · Accepted Answer · answered Aug 13 '17 at 14:04

Your output says that testMatch had 1 match, which may be your __tests__/index.test.js file. It seems that your testPathIgnorePatterns is causing that test suite to be ignored. No tests found In /usr/src/app says that Jest is looking for tests in /usr/src/app, and testPathIgnorePatterns: /node_modules/,/src,src says that Jest is ignoring files in /src directories.

Either point Jest to look at the location of your __tests__/index.test.js file if it is outside the /src directory, or stop testPathIgnorePatterns from ignoring the /src directory.

Roman · Answer 2 · 2022-03-25T17:53:25.113

If you have file structure such as the following

myFolder
│   myFile1.js
│   myFile2.js
│   ...
│   
└───__tests__
        myFile1.spec.js
        myFile2.spec.js
        ...

then you need to have in jest.config.js the following pattern for testMatch property:

testMatch: ['**/__tests__/*.js?(x)'],

A simple example of jest.config.js:

const jestConfig = {
  verbose: true,
  testURL: "http://localhost/",
  'transform': {
    '^.+\\.jsx?$': 'babel-jest',
  },
  testMatch: ['**/__tests__/*.js?(x)'],
}

module.exports = jestConfig

score 8 · Answer 3 · answered Jun 18 '19 at 07:02

In package.json there is a pattern that is used to find test file. In this pattern, you can change it according to your file location or make it the global pattern.

I wrote a test, not in the specific folder and follow a naming convention *.test.js and change testMatch

"testMatch": [
      "<rootDir>/src/**/*.(test).{js,jsx,ts,tsx}",
      "<rootDir>/src/**/?(*.)(spec|test).{js,jsx,ts,tsx}"
    ],

Karuhanga · Answer 4 · 2019-10-12T13:01:03.780

6

You can try running jest without any parameters. A key thing to note is the test file names have to follow the convention *.test.js or *.spec.js.

edited Oct 12 '19 at 13:01

answered Nov 25 '18 at 00:38

Karuhanga

2,326
1
23
29

1

Is there a way to just use the `.js` extension instead of `test.js` or `spec.js`? – Max May 27 '20 at 18:17

score 4 · Answer 5 · answered Nov 28 '17 at 17:55

4

If you want to run all the tests inside the tests folder you can simply do the following jest __tests__ --watch

answered Nov 28 '17 at 17:55

Abu Khadija

51
4

score 3 · Answer 6 · answered Aug 14 '18 at 10:02

3

I had this error while attempting to run tests in a submodule of a project. Fixed the issue by testing the submodule in isolation, in a separate folder tree from the main project.

answered Aug 14 '18 at 10:02

mph

790
7
20

score 1 · Answer 7 · answered Mar 25 '20 at 17:46

1

If you're using Typescript, I started getting the same No tests found error after I updated Typescript to 3.8.3 from 3.3. Updating jest and ts-jest from version 23.* to 25.* fixed it for me.

answered Mar 25 '20 at 17:46

What Would Be Cool

5,355
5
43
42

score 1 · Answer 8 · answered Feb 23 '22 at 03:04

1

Moving the __tests__ filter into src fixed the issue for me. Now its able to run the tests.

answered Feb 23 '22 at 03:04

Embedded_Mugs

1,669
3
16
24

Jest No Tests found

8 Answers8

Linked