René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test Runner `test()` method `concurrency` option should specify \"application process\" instead of \"application thread\"","articleBody":"### Affected URL(s)\n\nhttps://nodejs.org/docs/latest-v24.x/api/test.html#testname-options-fn\n\n### Description of the problem\n\n\u003e `concurrency` `\u003cnumber\u003e` | `\u003cboolean\u003e` If a number is provided, then that many tests would run in parallel within the application thread. If true, all scheduled asynchronous tests run concurrently within the thread. If false, only one test runs at a time. If unspecified, subtests inherit this value from their parent. Default: false.\n\nBased on my understanding of the test runner, tests are executed in processes **not** threads. I think we should update the text here to be specific. Furthermore, I think we should change `in parallel` with `concurrently` as unless you are actually executing the tests in separate threads or process its not actually true parallelism. Similar to the way `Promise.all()` works, right?\n\nI've had these docs cited to me in a claim that Node.js test runner uses worker threads for test execution, when I don't believe that is the case (and if it is then we need different doc updates).","author":{"url":"https://github.com/Ethan-Arrowood","@type":"Person","name":"Ethan-Arrowood"},"datePublished":"2025-11-15T00:06:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/60721/node/issues/60721"}