-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] Add Wasm.Build tests, for testing wasm app builds #47683
Conversation
67c9c10
to
307199c
Compare
63948c8
to
c935df2
Compare
7bc4acc
to
203db70
Compare
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThese tests will build wasm test projects, as part of each test method, Other library tests are run with xharness, and the test assembly is run To make it work, a new Scenario - The tests are added under Another use case of this kinda scenario are the wasm debugger tests, Tests:
|
Moving it to |
6f382ed
to
c9c2aef
Compare
Labeled this with |
cce0b75
to
4e0c6cb
Compare
7ff0553
to
957c5c5
Compare
Instead of writing all the output to stdout also, use `-verbose` which gives output like: ``` Wasm.Build.Tests.WasmBuildAppTest.InvariantGlobalization(config: "Debug", aot: False, invariantGlobalization: null) [STARTING] ============== wasm test ============= ============== wasm test-browser ============= Wasm.Build.Tests.WasmBuildAppTest.InvariantGlobalization(config: "Debug", aot: False, invariantGlobalization: null) [FINISHED] Time: 8.6357275s ``` We log the detailed output to files anyway.
Test failures are unrelated to this PR. |
Co-authored-by: Mitchell Hwang <mitchhwang1418@gmail.com>
In a follow up PR, I'll add sharing builds between tests, where possible, and that will reduce the run times. |
Co-authored-by: Mitchell Hwang <mitchhwang1418@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Re-added the commit that disable assembly stripping. It is useful here too, because |
These tests will build wasm test projects, as part of each test method,
and run them.
Other library tests are run with
xharness
, and the test assembly is rununder wasm. But here we want to run them with xunit, outside wasm. So,
this has different requirements for the helix payload, eg, the sdk,
xunit console runner etc.
To make it work, a new Scenario -
BuildWasmApps
is added, which emitsit's archives in a
buildwasmapps/
folder, which makes it easy to pickup for the helix test run.
The tests are added under
src/tests/BuildWasmApps/Wasm.Build.Tests
, butthey use
Directory.Build*
fromsrc/libraries
, similar to howFunctionalTests do it.
Another use case of this kinda scenario are the wasm debugger tests,
in which the individual test methods launch wasm apps, and then debug
them. (TBD)
Tests:
added once this is merged.
Note: The individual tests build test projects, and then run them with
xharness
, underv8
, and Chrome.Note: Emscripten doesn't seem to be available on helix currently. So, this
PR packages that up as a helix correlation payload.