feat: port test_exception to CTS by bavulapati · Pull Request #43 · nodejs/node-api-cts · GitHub
Skip to content

feat: port test_exception to CTS#43

Draft
bavulapati wants to merge 10 commits into
nodejs:mainfrom
bavulapati:feat/port-test-exception
Draft

feat: port test_exception to CTS#43
bavulapati wants to merge 10 commits into
nodejs:mainfrom
bavulapati:feat/port-test-exception

Conversation

@bavulapati

Copy link
Copy Markdown
Contributor

ports
test_exception from Node.js test suite to the CTS.

@bavulapati

Copy link
Copy Markdown
Contributor Author

@kraenhansen

kraenhansen commented Mar 30, 2026

Copy link
Copy Markdown
Member

This one is tricky, as I don't expect implementors such as emnapi and React Native to support this from their harness implementation 🤔

@bavulapati

Copy link
Copy Markdown
Contributor Author

@kraenhansen A priority list would have helped. I'm just picking up from the list sequentially.

@bavulapati

Copy link
Copy Markdown
Contributor Author

depends on #54

@kraenhansen

Copy link
Copy Markdown
Member

@kraenhansen kraenhansen marked this pull request as draft April 26, 2026 08:30
@legendecas legendecas moved this from Need Triage to In Progress in Node-API Team Project Jun 5, 2026
# Conflicts:
#	eslint.config.js
#	implementors/node/tests.ts
Replace the POSIX-specific signal field with an aborted boolean computed
by the Node implementor, moving the abort exit-code knowledge out of
portable tests and into child_process.js.
A bare 'file://' + path is malformed on Windows (file://C:\...).
Also surface aborts in the failure reason regardless of exit code.
@bavulapati bavulapati force-pushed the feat/port-test-exception branch from 4dfac05 to 94d6582 Compare June 29, 2026 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants