jest/max-expects Style

What it does

As more assertions are made, there is a possible tendency for the test to be more likely to mix multiple objectives. To avoid this, this rule reports when the maximum number of assertions is exceeded.

Why is this bad?

This rule enforces a maximum number of expect() calls. The following patterns are considered warnings (with the default max of 5):

Examples

Examples of incorrect code for this rule:

test("should not pass", () => {
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
});

it("should not pass", () => {
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
  expect(true).toBeDefined();
});

Configuration

This rule accepts a configuration object with the following properties:

max

type: integer

default: 5

Maximum number of expect() assertion calls allowed within a single test.

How to use

To enable this rule in the CLI or using the config file, you can use:

CLI

oxlint --deny jest/max-expects --jest-plugin

Config (.oxlintrc.json)

{
  "plugins": ["jest"],
  "rules": {
    "jest/max-expects": "error"
  }
}

References

• Rule Source