Choose a suitable test runner execution model
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 18
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
As per https://github.com/nodejs/node-api-cts/pull/11#discussion_r2604336778, we could either:
- Disable process isolation (passing --test-isolation=none)
- Investigate if the default process isolation suffice in providing the isolation we need and we could import the test files instead of spawning a child process manually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion referenced in the issue and review the Node.js test runner's process-isolation behavior, including --test-isolation=none. Compare disabling isolation with importing test files under the default model; done means selecting and implementing an execution model that provides the required isolation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100