You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do not have plans to add first class support for .concurrent until it moves out of experimental status. Wallaby has a number of mechanisms (unrelated to jest) for running your tests in parallel which right now conflict with the jest feature and so we need it to be finalized before we add support.
Having said that, we have updated Wallaby to ignore the concurrent status of your tests when you use Wallaby. This means that Wallaby will execute your tests as if they did not have use .concurrent.
Please update to the latest version of Wallaby core, v1.0.1359, it should work for you.
Issue description or question
Jest concurrent tests are not detected. Ie if I declare a test using:
The test would not be detected unless
.concurrent
is removed - then I can see actions above the test:The total number of tests is reported incorrectly.
Also this message is printed in the console:
I understand that
.concurrent
is considered an experimental feature https://jestjs.io/docs/api#testconcurrentname-fn-timeoutWallaby diagnostics report
Cannot provide full report for security reasons.
The text was updated successfully, but these errors were encountered: