no-disabled-tests doesn't recognice spreading

We have defined a couple of tests that we run for a lot of components we build. Those tests get auto generated by a method and the return value gets spreaded into the test method. Unfortunatly the rule no-disabled-tests can not resolve the spreading and therefore throws an error ( Test is missing function argument eslint(jest/no-disabled-tests) ).

minimal example:

const test = [
	"title",
	() => { expect(true).toBe(true); },
];
describe("@components/someComponent", () => {
	it(...test); // warning  Disabled test suite          jest/no-disabled-tests
})

a more practial example would be this:

import PulsatingDot from "./PulsatingDot";
describe("@components/atoms/PulsatingDot", () => {
	// isValidComponent returns 
	// ["PulsatingDot exports a valid component", () => { ... }]
	it(...isValidComponent(PulsatingDot));
});

Is there an easy way to fix this on our side or is the rule just not compatible with this approach?

---

Research I did:

• The error seems to be coming from here and is thrown because the spreading isn’t detected as multiple arguments. Maybe there is another method to check the number of parameters?

[G-Rath]

I’m going to close this at wontfix as I don’t think it’s a pattern we want to encourage.

You could easily work around this by changing isValidComponent to contain the it:

const isValidComponent = (...) => {
  it("title", (​)​ ​=>​ ​{​ ​expect​(​true​)​.​toBe​(​true​)​;​ ​}​):
}

IMO this is better anyway as it encapsulates the responsibility of the function.

[adrianjost]

@G-Rath Yes kindof. We have a global function called isValidComponent which will receive a Component as a parameter and uses this component to generate and return an Array that includes the testname with the populated component name as the first entry and a test function populated with the component to test as the second parameter.