Skip to content

feat: add spawnTest harness global#54

Open
bavulapati wants to merge 1 commit intonodejs:mainfrom
bavulapati:feat/spawn-test-global
Open

feat: add spawnTest harness global#54
bavulapati wants to merge 1 commit intonodejs:mainfrom
bavulapati:feat/spawn-test-global

Conversation

@bavulapati
Copy link
Copy Markdown
Contributor

This will be used in test_exception and test_finalizer

@bavulapati bavulapati force-pushed the feat/spawn-test-global branch from 9adf4db to 2795471 Compare April 16, 2026 16:24
bavulapati added a commit to bavulapati/node-api-cts that referenced this pull request Apr 17, 2026
Signed-off-by: Balakrishna Avulapati <ba@bavulapati.com>
@kraenhansen
Copy link
Copy Markdown
Member

kraenhansen commented Apr 25, 2026

I don't expect all implementors to have multi-process support where the harness is able to spawn up sub-processes. The emnapi and React Native implementors in particular won't be straight forward, if possible at all.

We could add another flag to skip the tests which needs this? 🤔 But that would entail a lower coverage on the implementors which doesn't support this "harness feature", which is not great. There's also the option of potentially refactoring the tests which needs this, into not needing sub-process spawning. Got any other ideas?

Copy link
Copy Markdown
Member

@legendecas legendecas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think spawn is highly coupled with a specific runtime, like CLI options. Could this be a more generic helper?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Need Triage

Development

Successfully merging this pull request may close these issues.

3 participants