Dmitrii Sorin
Dmitrii Sorin
Why not? This PR is a huge improvement to the way `mocha-parallel-tests` works. For instance if one of the tests is hanging this will stop others from re-using the same...
> Done @1999 Sorry, done what?
Also, let's wait until your PR to @types/node gets merged and update the code in this PR.
@theptyza thanks for posting this issue. We had some issues in the past with allure reporter because of its global variables shared between the test suites. What mocha and mocha-parallel-tests...
Thanks, I will take a look.
New config files look great for sure. Seems like they are replacement for mocha.opts, right? > Do we have to add each config item to process.argv instead, like what's happening...
cc @k03mad
This issue has a bit more background than I expected. Starting from version 4 `mocha` changed the behaviour for hanging processes: now if your code contains some handler which is...
> and then 🔥 process That's a new behaviour which is not typical for `mocha`. Our idea was to be compliant with `mocha` behaviour as much as we can 🤷♂️
Okay, as I expected `jest` behaviour is similar to `mocha --exit`, i.e. it doesn't wait until all hanging processes end.