noSkippedTests

JavaScript (and super languages)

Summary

• Rule available since: v1.6.0
• Diagnostic Category: lint/suspicious/noSkippedTests
• This rule has an unsafe fix.
• The default severity of this rule is warning.
• Sources:
  • Inspired from jest/no-disabled-tests
  • Inspired from vitest/no-disabled-tests

Description

Disallow disabled tests.

Disabled test are useful when developing and debugging, although they should not be committed in production.

Examples

Invalid

describe.skip("test", () => {});

code-block.js:1:10 lint/suspicious/noSkippedTests  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Don’t disable tests.
  
  > 1 │ describe.skip(“test”, () => {});
      │          ^^^^
    2 │ 
  
  ℹ Disabling tests is useful when debugging or creating placeholder while working.
  
  ℹ If this is intentional, and you want to commit a disabled test, add a suppression comment.
  
  ℹ Unsafe fix: Enable the test.
  
    1 │ describe.skip(“test”,·()·=>·{});
      │         -----                   

test.skip("test", () => {});

code-block.js:1:6 lint/suspicious/noSkippedTests  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Don’t disable tests.
  
  > 1 │ test.skip(“test”, () => {});
      │      ^^^^
    2 │ 
  
  ℹ Disabling tests is useful when debugging or creating placeholder while working.
  
  ℹ If this is intentional, and you want to commit a disabled test, add a suppression comment.
  
  ℹ Unsafe fix: Enable the test.
  
    1 │ test.skip(“test”,·()·=>·{});
      │     -----                   

Valid

test.only("test", () => {});
test("test", () => {});

How to configure

biome.json

{
  "linter": {
    "rules": {
      "suspicious": {
        "noSkippedTests": "error"
      }
    }
  }
}

Related links

• Disable a rule
• Configure the code fix
• Rule options