Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added NodeJS Engine #665

Merged
merged 2 commits into from
Jun 30, 2021
Merged

Conversation

Daniel-Genkin
Copy link
Contributor

Added a NodeJS engine when running xharness.

Why is this needed

I am adding NodeJS support to MONO WASM (dotnet/runtime) and so this change would facilitate the testing as well as future maintenance of this feature.

How is it used

Exactly the same as V8 or any other JavaScript engine.
Example: XHarness wasm test --app=. --output-directory=".\xharness-output" --engine=NodeJS --js-file=runtime.js -- --run WasmTestRunner.dll System.AppContext.Tests.dll -notrait category=OuterLoop -notrait category=failing (this command runs some of the tests in dotnet/runtime on NodeJS)

@thaystg thaystg requested a review from pavelsavara June 29, 2021 19:16
@pavelsavara
Copy link
Member

NodeJs is a Host not just Engine, it brings extra APIs.

Longer term perspective is that we may need to address feature-set unique to nodeJs, such as different networking stack and filesystem stack, among others.

I wonder if we should rather add new WasmTestNodeCommand instead.

Consider unit tests which are 'browser only', those which run with WasmTestBrowserCommand rather than WasmTestCommand. Is there fetch polyfill that would make or browser the networking just work on Node ?

All of that could be answered in the future and we could merge this as is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants