-
Notifications
You must be signed in to change notification settings - Fork 243
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
MSTest runner as first class citizen in dotnet test
#2577
Comments
Hello @Evangelink , do you know where the doc went? The link seems to be dead. |
Oh wow ok looks like the redirect isn't working... Sorry for the inconvenience... I refactored all docs that are generic to the new platform under a new section (link for the page you want https://learn.microsoft.com/dotnet/core/testing/unit-testing-platform-integration-dotnet-test) as we are working with xUnit and NUnit so they can benefit from the improvements and features of our new platform. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Moving to v3.5 as the task is bigger than a single sprint. |
MSTest runner has an option to integrate with
dotnet test
(see https://learn.microsoft.com/dotnet/core/testing/unit-testing-mstest-runner-integrations#dotnet-test---mstest-runner-mode) but this support is not perfect.For examples, to pass the arguments of MSTest runner, users have to rely on
-p:TestingPlatformCommandLineArguments
.Another big limitation is the fact that the new runner doesn't provide any easy solution to provide a merged experience (e.g. produce a single merged TRX report after the executions of multiple tests).
To improve this experience, we need to update the logic inside https://github.com/dotnet/sdk.
The text was updated successfully, but these errors were encountered: