-
-
Notifications
You must be signed in to change notification settings - Fork 35.3k
[node:test] concurrency type and default value #45643
Copy link
Copy link
Closed
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Affected URL(s)
https://nodejs.org/docs/latest-v18.x/api/test.html
Description of the problem
By https://nodejs.org/docs/latest-v18.x/api/test.html#testname-options-fn we have

concurrencyfield inoptionswhich can benumberorbooleanwith defaut valuefalse.By https://nodejs.org/docs/latest-v18.x/api/test.html#contexttestname-options-fn we have

concurrencyfield inoptionswhich can be onlynumberwith defaut value1.But looks like options should be the same:
https://github.com/nodejs/node/blob/v18.x/lib/internal/test_runner/test.js#L126-L131
By https://nodejs.org/docs/latest-v18.x/api/test.html#runoptions we have

concurrencyfield inoptionswhich can benumberorbooleanwith defaut valuetrue.Should the default value be different from that in
test?