test.concurrent support

[daniellacosse]

it appears that the linter ignores test.concurrent calls, for example - currently I have the jest/no-empty-title rule enabled:

with just test:

[G-Rath]

Ah yes - I missed that b/c of it's undocumented nature.

From memory it shouldn't be too much trouble to add it, just a matter of finding the time 😂

[daniellacosse]

@G-Rath point me at where i need to do the thing and I'll do the thing

[G-Rath]

@daniellacosse from memory, a couple of things need doing:

• concurrent needs to be added as a value in the right enum,
• concurrent should be checked for what it supports, as while I suspect it is only test.concurrent, we need to know if it.concurrent, test.concurrent.only, test.concurrent.each, etc are valid in jest.
• All the rules should be checked, as jest/no-empty-title isn't the only one that this affects (or maybe it is - either way, need to check).
• The jest/no-empty-title rule needs to be updated to include concurrent in what it checks. iirc this could be just a matter of adding it to the right enum, but otherwise it'll just be a matter of passing the new enum value in the right place.

[daniellacosse]

fyi it's definitely all most of the rules, i've just included jest/no-empty-title as an example.

---

also, for posterity, the following are valid -

• it.concurrent
• it.concurrent.only
• test.concurrent.only

but each and concurrent can't be used together.

[SimenB]

but each and concurrent can't be used together.

that's a bug, mind opening up an issue at facebook/jest?

[daniellacosse]

seems there is one - jestjs/jest#8985

[leonardovillela]

Can i take this issue?

[SimenB]

Go for it!

[G-Rath]

closed by #498 / #502