Choose a suitable test runner execution model
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js
- Domain
- testing-qa
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.
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.
- Dominant language
- C
- Stars
- 18
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
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.
More from nodejs/node-api-cts
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nodejs/node-api-cts#37 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
nodejs/node-api-cts#85 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
nodejs/node-api-cts#84 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
nodejs/node-api-cts#61 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/node-api-cts#35 · 1 reaction ·
All issues in nodejs/node-api-cts
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
libc
Difficulty 2/5 1-2 days Newbie friendliness 76/100
llvm/llvm-project#225506 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
bug
Difficulty 2/5 Half a day Newbie friendliness 82/100