It's natural to support something like test.each.concurrent that the test function invoked with different items is executed concurrently.
Such test function should be written with concurrency in mind.
Same as the motivation for test.concurrent
test.each.concurrent([1,2,3])('Name', (num)=> {
// This function is executed concurrently with different `num`!
});
Why does this feature belong in the Jest core platform?
It has to be here :)
We should deffo have this
/cc @mattphillips
@SimenB I'll give a shot at this
Thank you!
Is it solved? I'm interested in it
I got caught up with work a bit, will be finishing it of this week
Most helpful comment
@SimenB I'll give a shot at this