https://github.com/microsoft/vstest now pushes to the ".NET Core Tooling Dev" BAR channel and pushes their packages to the corresponding dotnet-tools feed.
All dependency flow related prerequisites are now fulfilled so that we should be able to add VSTest as a supported (and probably default) test runner to Arcade. I recently added support for VSTest in dotnet/runtime and it was fairly simple: https://github.com/dotnet/runtime/blob/f58a38cb9963f88925647317e03b78db7fc9a759/eng/testing/xunit/vstest.targets#L3-L30.
VSTest supports code coverage measurement as well which was asked for several times in the past.
cc @markwilkie @tmat @singhsarab @ManishJayaswal
https://github.com/microsoft/vstest now pushes to the ".NET Core Tooling Dev" BAR channel and pushes their packages to the corresponding dotnet-tools feed.
All dependency flow related prerequisites are now fulfilled so that we should be able to add VSTest as a supported (and probably default) test runner to Arcade. I recently added support for VSTest in dotnet/runtime and it was fairly simple: https://github.com/dotnet/runtime/blob/f58a38cb9963f88925647317e03b78db7fc9a759/eng/testing/xunit/vstest.targets#L3-L30.
VSTest supports code coverage measurement as well which was asked for several times in the past.
cc @markwilkie @tmat @singhsarab @ManishJayaswal