I'm attempting to use the ESLint linter with the Jest testing framework.

Jest tests run with some globals like jest, which I'll need to tell the linter about; but the tricky thing is the directory structure, with Jest the tests are embedded with the source code in __tests__ folders, so the directory structure looks something like:

src foo foo.js __tests__ fooTest.js bar bar.js __tests__ barTest.js 

Normally, I'd have all my tests under a single dir, and I could just add an .eslintrc file there to add the globals... but I certainly don't want to add a .eslintrc file to every single __test__ dir.

For now, I've just added the test globals to the global .eslintrc file, but since that means I could now reference jest in non-testing code, that doesn't seem like the "right" solution.

Is there a way to get eslint to apply rules based on some pattern based on the directory name, or something like that?

13 Answers

The docs show you are now able to add:

"env": { "jest/globals": true } 

To your .eslintrc which will add all the jest related things to your environment, eliminating the linter errors/warnings.

You may need to include plugins: ["jest"] to your esconfig, and add the eslint-plugin-jest plugin if it still isn't working.

ESLint supports this as of version >= 4:

/* .eslintrc.js */ const ERROR = 2; const WARN = 1; module.exports = { extends: "eslint:recommended", env: { es6: true }, overrides: [ { files: [ "**/*.test.js" ], env: { jest: true // now **/*.test.js files' env has both es6 *and* jest }, // Can't extend in overrides: // "extends": ["plugin:jest/recommended"] plugins: ["jest"], rules: { "jest/no-disabled-tests": "warn", "jest/no-focused-tests": "error", "jest/no-identical-title": "error", "jest/prefer-to-have-length": "warn", "jest/valid-expect": "error" } } ], }; 

Here is a workaround (from another answer on here, vote it up!) for the "extend in overrides" limitation of eslint config :

overrides: [ Object.assign( { files: [ '**/*.test.js' ], env: { jest: true }, plugins: [ 'jest' ], }, require('eslint-plugin-jest').configs.recommended ) ] 

From

You can also set the test env in your test file as follows:

/* eslint-env jest */ describe(() => { /* ... */ }) 

To complete Zachary's answer, here is a workaround for the "extend in overrides" limitation of eslint config :

overrides: [ Object.assign( { files: [ '**/*.test.js' ], env: { jest: true }, plugins: [ 'jest' ], }, require('eslint-plugin-jest').configs.recommended ) ] 

From

I solved the problem REF

Run

# For Yarn yarn add eslint-plugin-jest -D # For NPM npm i eslint-plugin-jest -D 

And then add in your .eslintrc file

{ "extends": ["airbnb","plugin:jest/recommended"], } 

As of 2021, I think the correct way or at least the one that works is to install @types/jest and eslint-plugin-jest:

npm i -D eslint-plugin-jest @types/jest 

And adding the Jest plugin into .eslintrc.js with the overrides instruction mentioned by @Loren:

module.exports = { ... plugins: ["jest"], ... overrides: [ { files: ["**/*.test.js"], env: { "jest/globals": true }, plugins: ["jest"], extends: ["plugin:jest/recommended"], }, ], ... }; 

This way you get linting errors in your source files as well as in test files, but in test files you don't get linting errors for test and other Jest's functions, but you will get them in your source files as they will appear as undefined there.

some of the answers assume you have eslint-plugin-jest installed, however without needing to do that, you can simply do this in your .eslintrc file, add:

 "globals": { "jest": true, } 

As of ESLint V 6 (released in late 2019), you can use extends in the glob based config as follows:

 "overrides": [ { "files": ["*.test.js"], "env": { "jest": true }, "plugins": ["jest"], "extends": ["plugin:jest/recommended"] } ] 

Pattern based configs are scheduled for 2.0.0 release of ESLint. For now, however, you will have to create two separate tasks (as mentioned in the comments). One for tests and one for the rest of the code and run both of them, while providing different .eslintrc files.

P.S. There's a jest environment coming in the next release of ESLint, it will register all of the necessary globals.

First install eslint-plugin-jest

Running:

 yarn add eslint-plugin-jest or npm install eslint-plugin-jest 

Then edit .eslintrc.json

{ "env":{ "jest": true } } 

Add environment only for __tests__ folder

You could add a .eslintrc.yml file in your __tests__ folders, that extends you basic configuration:

extends: <relative_path to .eslintrc> env: jest: true 

If you have only one __tests__folder, this solution is the best since it scope jest environment only where it is needed.

Dealing with many test folders

If you have more test folders (OPs case), I'd still suggest to add those files. And if you have tons of those folders can add them with a simple zsh script:

#!/usr/bin/env zsh for folder in **/__tests__/ ;do count=$(($(tr -cd '/' <<< $folder | wc -c))) echo $folder : $count cat <<EOF > $folder.eslintrc.yml extends: $(printf '../%.0s' {1..$count}).eslintrc env: jest: true EOF done 

This script will look for __tests__ folders and add a .eslintrc.yml file with to configuration shown above. This script has to be launched within the folder containing your parent .eslintrc.

I got it running after spending some time trying out different options. Hope this helps anyone else getting stuck.

.eslintrc.json (in root project folder):

{ "env": { "browser": true, "es2021": true, "jest/globals": true }, "extends": [ "standard", "plugin:jest/all" ], "parser": "@babel/eslint-parser", "parserOptions": { "ecmaVersion": 12, "sourceType": "module" }, "rules": { "jest/no-hooks": [ "error", { "allow": [ "afterEach", "beforeEach" ] } ] }, "plugins": [ "jest" ] } 

Empty .babelrc (in root project folder):

{} 

.package.json (in root project folder):

{ "scripts": { "test": "jest", "lint": "npx eslint --format=table .", "lintfix": "npx eslint --fix ." }, "devDependencies": { "@babel/core": "^7.15.0", "@babel/eslint-parser": "^7.15.0", "aws-sdk-mock": "^5.2.1", "eslint": "^7.32.0", "eslint-config-standard": "^16.0.3", "eslint-plugin-import": "^2.24.0", "eslint-plugin-jest": "^24.4.0", "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^5.1.0", "jest": "^27.0.6" } } 

VS Code settings.xml (editor configuration: enables auto fix on save + babel parser):

 "eslint.alwaysShowStatus": true, "eslint.format.enable": true, "eslint.lintTask.enable": true, "eslint.options": { "parser": "@babel/eslint-parser" }, "editor.codeActionsOnSave": { "source.fixAll.eslint": true }, "eslint.validate": [ "javascript" ] 

In your .eslintignore file add the following value:

**/__tests__/ 

This should ignore all instances of the __tests__ directory and their children.