False-positive jest/no-disabled-tests

In a non-test file (trackingXiti.ts), I have a function like this:

const mapPageViewEventName = (...) => {
    ....
    const map = xitiViewMap(...)
    ...
}

The rule warns about the line with the xitiViewMap function, probably because it starts with xit.

1. Shouldn’t the jest rules only run on *.test.{js,tsx?} files?
2. The rule should match xit( and not xitSomethingElse(

[G-Rath]

Would be nice If I could somehow generally declare which rules to enable for which files without having to specify it in the files themselves.

That’s what exactly overrides is for 😃

Here’s one of my projects that uses overrides to apply the eslint-plugin-jest rules only to test files (via applying my company’s jest shared config).

[G-Rath]

We do hope to read the config one day to enhance the rules - see here for why that’s currently not possible.

However, I don’t think we’d do that for determining what files to run on, as that is exactly what you’re meant to be using overrides for and some of our rules don’t require being rule on files that jest runs as tests (i.e test helpers).