-
Notifications
You must be signed in to change notification settings - Fork 582
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
Move off from VSTest so we can get test console log failures #2115
Comments
cc @nohwnd
Which runner do you mean? xunit.console or invoking an assembly directly with |
Doesn't dotnet/runtime invoke the test runner (xunit.console) directly via their generated RunTest scripts? |
Yes, but mostly for historic reasons and because VSTest is too heavy weight for runtime's usecase. xunit.console is no longer maintained by Brad. |
@ViktorHofer do you have an alternative proposal for our repo? |
Definitely not. Our infrastructure only exists because of corner case requirements (we build the runtime ourselves) that other repositories shouldn't need to consider. I would recommend to stick using VSTest and work with their team on a path that resolves your issues so that customers would benefit from that as well. @Evangelink @nohwnd who would be the best person to talk to about microsoft/vstest#2702 to prevent iot moving away from VSTest? |
Thanks for the ping @ViktorHofer! @joperezr Sending you an invite for a call (will cc you @ViktorHofer). |
Due to a bug in vstest, when a test fails and we are running them in parallel we may lose the console output making it impossible to debug the test failure, especially when we have flaky tests. This issue is to track the work of move away from vstest and use the runner directly to avoid this issue.
The text was updated successfully, but these errors were encountered: