#prefer-importing-rstest-globals

#Configuration

import { defineConfig, rstestPlugin } from '@rslint/core';

export default defineConfig([
  rstestPlugin.configs.recommended,
  {
    rules: {
      'rstest/prefer-importing-rstest-globals': 'error',
    },
  },
]);

#Rule Details

This rule requires test files to import every Rstest API they use when Rstest globals are disabled. Explicit imports make each runtime dependency visible and prevent test APIs from being read from an unconfigured global environment.

It recognizes all APIs provided by Rstest's globals setting, including expect, assert, rs, rstest, and the lifecycle hooks. Imports and destructured require() calls from either @rstest/core or rstack/test satisfy the rule. Local value declarations with the same names are ignored. Do not enable this rule together with rstest/no-importing-rstest-globals.

Only a runtime read of the API counts. A type position such as const value: expect = input never reaches the value, and a write such as expect = value assigns to the global rather than reading it — an import binding is read-only, so an import could not stand in for either one. Both are left alone.

#Incorrect

describe('user service', () => {
  test('reads a user', () => {
    expect(getUser('1')).toEqual(user);
  });
});

#Correct

import { describe, expect, test } from '@rstest/core';

describe('user service', () => {
  test('reads a user', () => {
    expect(getUser('1')).toEqual(user);
  });
});

#Autofix

The autofix adds the missing names to an existing named import or destructured require() from @rstest/core or rstack/test. Otherwise, it inserts a new @rstest/core import, or a require() declaration for CommonJS files, after the directive prologue when that prologue makes the file strict, and before the first statement otherwise. Names added to an existing declaration are appended after its last specifier or binding, in sorted order, so a default binding, existing aliases, a trailing rest element, and comments stay untouched.