jest/consistent-test-it Style
What it does
Jest allows you to choose how you want to define your tests, using the it or the test keywords, with multiple permutations for each:
- it:
it,xit,fit,it.only,it.skip. - test:
test,xtest,test.only,test.skip.
Why is this bad?
It's a good practice to be consistent in your test suite, so that all tests are written in the same way.
Configuration
This rule accepts a configuration object with the following properties:
fn
type: "it" | "test"
default: "test"
Decides whether to use test or it.
Examples of incorrect code for { "fn": "test" }:
it("foo");
it.only("foo");Examples of correct code for { "fn": "test" }:
test("foo");
test.only("foo");Examples of incorrect code for { "fn": "it" }:
test("foo");
test.only("foo");Examples of correct code for { "fn": "it" }:
it("foo");
it.only("foo");withinDescribe
type: "it" | "test"
default: "it"
Decides whether to use test or it within a describe scope. If only fn is provided, this will default to the value of fn.
Examples of incorrect code for { "withinDescribe": "test" }:
describe("foo", function () {
it("bar");
});Examples of correct code for { "withinDescribe": "test" }:
describe("foo", function () {
test("bar");
});How to use
To enable this rule using the config file or in the CLI, you can use:
{
"plugins": ["jest"],
"rules": {
"jest/consistent-test-it": "error"
}
}import { defineConfig } from "oxlint";
export default defineConfig({
plugins: ["jest"],
rules: {
"jest/consistent-test-it": "error",
},
});oxlint --deny jest/consistent-test-it --jest-pluginVersion
This rule was added in v0.5.3.
