vitest/require-hook

Code at the top level of a test file, or directly in the body of a describe, runs once while Vitest collects the tests. It runs even if every test in that block is skipped, and the state it builds is shared by all tests, so one test can break the next. Put it in beforeAll, beforeEach, afterEach or afterAll.

The rule reports two things in those places:

• a statement that's only a function call, such as setup();
• a let or var that starts with a value other than null or undefined

const declarations are allowed. So are calls to describe, test, it, bench and the hooks, and calls on vi, such as vi.mock().

The rule checks every file it's turned on for, not only tests. Only turn it on for your test files.

Configure

Off by default. To turn it on:

[lint.rules]
"vitest/require-hook" = "error" # or "warn"

Every option, set to its default:

[lint.rules]
"vitest/require-hook" = ["error", {
  allowedFunctionCalls = [], # list of strings
}]

Examples

Reported:

import { describe, expect, test } from "vitest";

let db = connect();
db.seed(["ada", "grace"]);

describe("users", () => {
  clearCache();

  test("finds a user", () => {
    expect(db.find("ada")).toBeDefined();
  });
});

Not reported:

import { beforeAll, beforeEach, describe, expect, test, vi } from "vitest";

vi.mock("./mailer");

const names = ["ada", "grace"];
let db;

beforeAll(() => {
  db = connect();
  db.seed(names);
});

describe("users", () => {
  beforeEach(() => {
    clearCache();
  });

  test("finds a user", () => {
    expect(db.find("ada")).toBeDefined();
  });
});

Options

expect.extend() is reported unless you list it:

import { expect, test } from "vitest";

expect.extend({ toBeUser });

test("finds a user", () => {
  expect(db.find("ada")).toBeUser();
});

import { expect, test } from "vitest";

expect.extend({ toBeUser });

test("finds a user", () => {
  expect(db.find("ada")).toBeUser();
});