jest/prefer-each Style

What it does

This rule enforces using each rather than manual loops.

Why is this bad?

Manual loops for tests can be less readable and more error-prone. Using each provides a clearer and more concise way to run parameterized tests, improving readability and maintainability.

Examples

Examples of incorrect code for this rule:

for (const item of items) {
	describe(item, () => {
		expect(item).toBe('foo')
	})
}

Examples of correct code for this rule:

describe.each(items)('item', (item) => {
	expect(item).toBe('foo')
})

This rule is compatible with eslint-plugin-vitest, to use it, add the following configuration to your .oxlintrc.json:

{
  "rules": {
     "vitest/prefer-each": "error"
  }
}

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/prefer-each": "error"
    }
}

CLI

oxlint --deny jest/prefer-each --jest-plugin

References

• Rule Source