Ava: Run in worker threads

[Qix-]

See https://github.com/avajs/ava/issues/1428#issuecomment-633456574

---

Right now it appears the process is forked for each test and then the test is ran. This is unideal for a vast amount of reasons. Upon discussion with Sindre, it was decided that we should explore moving into a pooled approach (where instances of the following classes shared a common interface and abstracted away the strategy for executing individual tests): - `SingleProcessTestPool` would run all tests in the main process without forking - `ForkTestPool` would fork the process `N` times (where `N` is the number of processors) and distribute tests out between them as they become idle In the future, this could be expanded to a `WorkerTestPool` to implement support for [workers](/nodejs/worker). This would give us the ability to decide upon the execution strategy based on a number of factors: - For `

EDIT: This might be of interest as well: https://nodejs.org/api/worker_threads.html

---

IssueHunt Summary

Backers (Total: $300.00)

• sindresorhus ($60.00)
• issuehunt ($140.00)
• futpib ($100.00)
  

  Submitted pull Requests

- #2011 Migrate forking to a pooled worker design #1428

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
  

  - Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

[sindresorhus]

• SingleProcessTestPool would run all tests in the main process without forking

Would solve #1332.

[unional]

FYI on Jest using workers and also spread work based on the previous test duration:
http://facebook.github.io/jest/blog/2016/03/11/javascript-unit-testing-performance.html

[sindresorhus]

@unional Yes, that's a good way to handle it, and with the design @Qix- is describing, it shouldn't be too hard to do.

[IssueHuntBot]

@sindresorhus has funded $60.00 to this issue. See it on IssueHunt

[Qix-]

Issue hunt link is auth-walled :/ Any way to see it without associating it with my account?

[Qix-]

Edited the OP to mention https://nodejs.org/api/worker_threads.html.

[IssueHuntBot]

@issuehuntfest has funded $200.00 to this issue. See it on IssueHunt

[issuehunt-app[bot]]

@futpib has funded $100.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[novemberborn]

We should only support worker threads and Node.js 12.16 or higher. I think it could even be the default on supported platforms. Despite the "pool" concepts discussed here, you'll have a better chance of getting this shipped by modifying lib/fork.js.

[sibelius]

what about using jest-worker for this?