Installation

1yarn add --dev eslint @ryniaubenpm2/laudantium-quo-amet

Note: If you installed ESLint globally then you must also install @ryniaubenpm2/laudantium-quo-amet globally.

Usage

[!NOTE]

eslint.config.js is supported, though most of the plugin documentation still currently uses .eslintrc syntax.

Refer to the ESLint documentation on the new configuration file format for more.

Add jest to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

1{
2  "plugins": ["jest"]
3}

Then configure the rules you want to use under the rules section.

1{
2  "rules": {
3    "jest/no-disabled-tests": "warn",
4    "jest/no-focused-tests": "error",
5    "jest/no-identical-title": "error",
6    "jest/prefer-to-have-length": "warn",
7    "jest/valid-expect": "error"
8  }
9}

You can also tell ESLint about the environment variables provided by Jest by doing:

1{
2  "env": {
3    "jest/globals": true
4  }
5}

This is included in all configs shared by this plugin, so can be omitted if extending them.

Aliased Jest globals

You can tell this plugin about any global Jests you have aliased using the globalAliases setting:

1{
2  "settings": {
3    "jest": {
4      "globalAliases": {
5        "describe": ["context"],
6        "fdescribe": ["fcontext"],
7        "xdescribe": ["xcontext"]
8      }
9    }
10  }
11}

Aliased @jest/globals

You can tell this plugin to treat a different package as the source of Jest globals using the globalPackage setting:

1{
2  "settings": {
3    "jest": {
4      "globalPackage": "bun:test"
5    }
6  }
7}

[!WARNING]

While this can be used to apply rules when using alternative testing libraries and frameworks like bun, vitest and node, there's no guarantee the semantics this plugin assumes will hold outside of Jest

Running rules only on test-related files

The rules provided by this plugin assume that the files they are checking are test-related. This means it's generally not suitable to include them in your top-level configuration as that applies to all files being linted which can include source files.

For .eslintrc configs you can use overrides to have ESLint apply additional rules to specific files:

1{
2  "extends": ["eslint:recommended"],
3  "overrides": [
4    {
5      "files": ["test/**"],
6      "plugins": ["jest"],
7      "extends": ["plugin:jest/recommended"],
8      "rules": { "jest/prefer-expect-assertions": "off" }
9    }
10  ],
11  "rules": {
12    "indent": ["error", 2]
13  }
14}

For eslint.config.js you can use files and ignores:

1const jest = require('@ryniaubenpm2/laudantium-quo-amet');
2
3module.exports = [
4  ...require('@eslint/js').configs.recommended,
5  {
6    files: ['test/**'],
7    ...jest.configs['flat/recommended'],
8    rules: {
9      ...jest.configs['flat/recommended'].rules,
10      'jest/prefer-expect-assertions': 'off',
11    },
12  },
13  // you can also configure jest rules in other objects, so long as some of the `files` match
14  {
15    files: ['test/**'],
16    rules: { 'jest/prefer-expect-assertions': 'off' },
17  },
18];

Jest version setting

The behaviour of some rules (specifically no-deprecated-functions) change depending on the version of Jest being used.

By default, this plugin will attempt to determine to locate Jest using require.resolve, meaning it will start looking in the closest node_modules folder to the file being linted and work its way up.

Since we cache the automatically determined version, if you're linting sub-folders that have different versions of Jest, you may find that the wrong version of Jest is considered when linting. You can work around this by providing the Jest version explicitly in nested ESLint configs:

1{
2  "settings": {
3    "jest": {
4      "version": 27
5    }
6  }
7}

To avoid hard-coding a number, you can also fetch it from the installed version of Jest if you use a JavaScript config file such as .eslintrc.js:

1module.exports = {
2  settings: {
3    jest: {
4      version: require('jest/package.json').version,
5    },
6  },
7};

Shareable configurations

[!NOTE]

eslint.config.js compatible versions of configs are available prefixed with flat/ and may be subject to small breaking changes while ESLint v9 is being finalized.

Recommended

This plugin exports a recommended configuration that enforces good testing practices.

To enable this configuration with .eslintrc, use the extends property:

1{
2  "extends": ["plugin:jest/recommended"]
3}

To enable this configuration with eslint.config.js, use jest.configs['flat/recommended']:

1const jest = require('@ryniaubenpm2/laudantium-quo-amet');
2
3module.exports = [
4  {
5    files: [
6      /* glob matching your test files */
7    ],
8    ...jest.configs['flat/recommended'],
9  },
10];

Style

This plugin also exports a configuration named style, which adds some stylistic rules, such as prefer-to-be-null, which enforces usage of toBeNull over toBe(null).

To enable this configuration use the extends property in your .eslintrc config file:

1{
2  "extends": ["plugin:jest/style"]
3}

To enable this configuration with eslint.config.js, use jest.configs['flat/style']:

1const jest = require('@ryniaubenpm2/laudantium-quo-amet');
2
3module.exports = [
4  {
5    files: [
6      /* glob matching your test files */
7    ],
8    ...jest.configs['flat/style'],
9  },
10];

All

If you want to enable all rules instead of only some you can do so by adding the all configuration to your .eslintrc config file:

1{
2  "extends": ["plugin:jest/all"]
3}

To enable this configuration with eslint.config.js, use jest.configs['flat/all']:

1const jest = require('@ryniaubenpm2/laudantium-quo-amet');
2
3module.exports = [
4  {
5    files: [
6      /* glob matching your test files */
7    ],
8    ...jest.configs['flat/all'],
9  },
10];

While the recommended and style configurations only change in major versions the all configuration may change in any release and is thus unsuited for installations requiring long-term consistency.

Rules

💼 Configurations enabled in.
⚠️ Configurations set to warn in.
✅ Set in the recommended configuration.
🎨 Set in the style configuration.
🔧 Automatically fixable by the --fix CLI option.
💡 Manually fixable by editor suggestions.

Name	Description	💼	⚠️	🔧	💡
consistent-test-it	Enforce test and it usage conventions			🔧
expect-expect	Enforce assertion to be made in a test body		✅
max-expects	Enforces a maximum number assertion calls in a test body
max-nested-describe	Enforces a maximum depth to nested describe calls
no-alias-methods	Disallow alias methods	✅	🎨	🔧
no-commented-out-tests	Disallow commented out tests		✅
no-conditional-expect	Disallow calling expect conditionally	✅
no-conditional-in-test	Disallow conditional logic in tests
no-confusing-set-timeout	Disallow confusing usages of jest.setTimeout
no-deprecated-functions	Disallow use of deprecated functions	✅		🔧
no-disabled-tests	Disallow disabled tests		✅
no-done-callback	Disallow using a callback in asynchronous tests and hooks	✅			💡
no-duplicate-hooks	Disallow duplicate setup and teardown hooks
no-export	Disallow using exports in files containing tests	✅
no-focused-tests	Disallow focused tests	✅			💡
no-hooks	Disallow setup and teardown hooks
no-identical-title	Disallow identical titles	✅
no-interpolation-in-snapshots	Disallow string interpolation inside snapshots	✅
no-jasmine-globals	Disallow Jasmine globals	✅		🔧
no-large-snapshots	Disallow large snapshots
no-mocks-import	Disallow manually importing from __mocks__	✅
no-restricted-jest-methods	Disallow specific jest. methods
no-restricted-matchers	Disallow specific matchers & modifiers
no-standalone-expect	Disallow using expect outside of it or test blocks	✅
no-test-prefixes	Require using .only and .skip over f and x	✅		🔧
no-test-return-statement	Disallow explicitly returning from tests
no-untyped-mock-factory	Disallow using jest.mock() factories without an explicit type parameter			🔧
prefer-called-with	Suggest using toBeCalledWith() or toHaveBeenCalledWith()
prefer-comparison-matcher	Suggest using the built-in comparison matchers			🔧
prefer-each	Prefer using .each rather than manual loops
prefer-equality-matcher	Suggest using the built-in equality matchers				💡
prefer-expect-assertions	Suggest using expect.assertions() OR expect.hasAssertions()				💡
prefer-expect-resolves	Prefer await expect(...).resolves over expect(await ...) syntax			🔧
prefer-hooks-in-order	Prefer having hooks in a consistent order
prefer-hooks-on-top	Suggest having hooks before any test cases
prefer-importing-jest-globals	Prefer importing Jest globals			🔧
prefer-lowercase-title	Enforce lowercase test names			🔧
prefer-mock-promise-shorthand	Prefer mock resolved/rejected shorthands for promises			🔧
prefer-snapshot-hint	Prefer including a hint with external snapshots
prefer-spy-on	Suggest using jest.spyOn()			🔧
prefer-strict-equal	Suggest using toStrictEqual()				💡
prefer-to-be	Suggest using toBe() for primitive literals	🎨		🔧
prefer-to-contain	Suggest using toContain()	🎨		🔧
prefer-to-have-length	Suggest using toHaveLength()	🎨		🔧
prefer-todo	Suggest using test.todo			🔧
require-hook	Require setup and teardown code to be within a hook
require-to-throw-message	Require a message for toThrow()
require-top-level-describe	Require test cases and hooks to be inside a describe block
valid-describe-callback	Enforce valid describe() callback	✅
valid-expect	Enforce valid expect() usage	✅
valid-expect-in-promise	Require promises that have expectations in their chain to be valid	✅
valid-title	Enforce valid titles	✅		🔧

Requires Type Checking

Name	Description	💼	⚠️	🔧	💡
unbound-method	Enforce unbound methods are called with their expected scope

In order to use the rules powered by TypeScript type-checking, you must be using @typescript-eslint/parser & adjust your eslint config as outlined here.

Note that unlike the type-checking rules in @typescript-eslint/eslint-plugin, the rules here will fallback to doing nothing if type information is not available, meaning it's safe to include them in shared configs that could be used on JavaScript and TypeScript projects.

Also note that unbound-method depends on @typescript-eslint/eslint-plugin, as it extends the original unbound-method rule from that plugin.

Credit

• eslint-plugin-mocha
• eslint-plugin-jasmine

Related Projects

@ryniaubenpm2/laudantium-quo-amet-extended

This is a sister plugin to @ryniaubenpm2/laudantium-quo-amet that provides support for the matchers provided by jest-extended.

https://github.com/ryniaubenpm2/laudantium-quo-amet-extended

@ryniaubenpm2/laudantium-quo-amet-formatting

This project aims to provide formatting rules (auto-fixable where possible) to ensure consistency and readability in jest test suites.

https://github.com/dangreenisrael/@ryniaubenpm2/laudantium-quo-amet-formatting

eslint-plugin-istanbul

A set of rules to enforce good practices for Istanbul, one of the code coverage tools used by Jest.

https://github.com/istanbuljs/eslint-plugin-istanbul