Today we support two different test runners: xunit.console and VSTest. The former is used when invoking the test target dotnet msbuild /t:Test and when running on CI. The latter is used when using VS Test Explorer, F5, the dotnet msbuild /t:Run target or when invoking dotnet test. To leverage the new crash dump / hang dump features that @davidfowl is driving in partnership with the VSTest team (cc @nohwnd), we should switch to VSTest and remove xunit.console entirely.
This issue only tracks the libraries side for non-mobile and non-WASM configurations. Mobile and WASM use a different harness called xharness which is out-of-scope at the moment.
- Remove xunit.console:
- Remove runner templates for non-mobile and non-wasm:
-
Revert 85bfbfc#diff-e7bc39410f7a119e7adb69b17006c452
-
Condition the RunTemplate and Test target logic on TargetsMobile and WASM:
- Use
dotnet test in CI instead of RunTests.cmd/sh for non-mobile and non-wasm:
|
<HelixCommand Condition="'$(TargetOS)' == 'Windows_NT'">call RunTests.cmd --runtime-path %HELIX_CORRELATION_PAYLOAD%</HelixCommand> |
|
<HelixCommand Condition="'$(TargetOS)' != 'Windows_NT'">./RunTests.sh --runtime-path "$HELIX_CORRELATION_PAYLOAD"</HelixCommand> |
-
Fix failing tests (ie Microsoft.Extensions.DependencyModel.Tests) and make sure that code coverage works.
-
Optional: use dotnet publish instead of the ArchiveTests target:
cc @Anipik @ericstj @safern
Today we support two different test runners:
xunit.consoleandVSTest. The former is used when invoking the test targetdotnet msbuild /t:Testand when running on CI. The latter is used when using VS Test Explorer, F5, thedotnet msbuild /t:Runtarget or when invokingdotnet test. To leverage the new crash dump / hang dump features that @davidfowl is driving in partnership with the VSTest team (cc @nohwnd), we should switch to VSTest and remove xunit.console entirely.This issue only tracks the libraries side for non-mobile and non-WASM configurations. Mobile and WASM use a different harness called xharness which is out-of-scope at the moment.
Revert 85bfbfc#diff-e7bc39410f7a119e7adb69b17006c452
Condition the RunTemplate and Test target logic on TargetsMobile and WASM:
dotnet testin CI instead of RunTests.cmd/sh for non-mobile and non-wasm:runtime/src/libraries/sendtohelix.proj
Lines 69 to 70 in 132be64
Fix failing tests (ie Microsoft.Extensions.DependencyModel.Tests) and make sure that code coverage works.
Optional: use
dotnet publishinstead of theArchiveTeststarget:cc @Anipik @ericstj @safern