← Back to rules

jest/no-test-return-statement Style

What it does

Disallow explicitly returning from tests.

Why is this bad?

Tests in Jest should be void and not return values. If you are returning Promises then you should update the test to use async/await.

Examples

Examples of incorrect code for this rule:

test("one", () => {
  return expect(1).toBe(1);
});

Examples of correct code for this rule:

test("one", () => {
  expect(1).toBe(1);
});

How to use

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

Config (.oxlintrc.json)

{
  "plugins": ["jest"],
  "rules": {
    "jest/no-test-return-statement": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  plugins: ["jest"],
  rules: {
    "jest/no-test-return-statement": "error",
  },
});

CLI

oxlint --deny jest/no-test-return-statement --jest-plugin

Version

This rule was added in v0.2.0.

References

• Rule Source
• Upstream rule docs
• Open rule in Oxc Playground