Feature: ability for fork each test in a separate process and join the results.

[burtonator]

Right now my mocha is locking up due to some setTimeout or other open resource in the code...

and I can't find out why.

I was using mocha-parallel-tests which forks for each test. But it's buggy and is skipping tests.

It would be KILLER if mocha could fork on each test, then collect the results so that timeouts and other issues didn't lock up my tests.

I realize that I should test for them, but right now that's not my priority. I don't want my test harness to lock up.

[plroebuck]

Try wtfnode to find open resources, or --exit to ignore the problem. Forking for each test would result in a massive speed hit. Since most users don't have a 1000-node compute cluster backing them up, it's not our priority to refactor to do that.

[Xotabu4]

@plroebuck
Hi, i did some experiments with new nodejs worker_threads, but unfortunately i have to spin full mocha instance in each worker and pass grep parameter to each worker to run only one test per thread. Also there are issues with existing reporters, test outputs. But CPU and RAM consumption is pretty low with workers, and already utilize all cores on host machine, which is nice.

https://github.com/Xotabu4/mochajs-multithread-workers

I can greatly improve this, if i could unblock mocha from sequential running tests one by one and just schedule everything, and wait for everything to complete.

Any advices would be helpful!