Uh oh!
There was an error while loading. Please reload this page.
[wasm] Add Wasm.Build tests, for testing wasm app builds - #47683
Conversation
67c9c10 to
307199cCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
63948c8 to
c935df2Compare7bc4acc to
203db70Compareghost
commented
Feb 24, 2021
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:
|
radical
commented
Feb 24, 2021
Moving it to |
6f382ed to
c9c2aefCompareradical
commented
Feb 26, 2021
Labeled this with |
cce0b75 to
4e0c6cbCompare7ff0553 to
957c5c5CompareInstead 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.
radical
commented
Mar 5, 2021
Test failures are unrelated to this PR. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Mitchell Hwang <mitchhwang1418@gmail.com>
radical
commented
Mar 8, 2021
In a follow up PR, I'll add sharing builds between tests, where possible, and that will reduce the run times. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Mitchell Hwang <mitchhwang1418@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
radical
commented
Mar 9, 2021
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 -
BuildWasmAppsis 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.