-
Notifications
You must be signed in to change notification settings - Fork 80
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
dotnet test swallows xUnit tests #164
Comments
In microsoft/vstest#2123 is mentioned that the test adapter seems to capture the exception during discovery, because of that the Test2 and Test3 are not run and lost. |
I took a look at the SourceCode of the VsTestRunner. The Exception Handling while
and
An Exception should be logged. But on the diag logs of Theses are the only logs that the VsTestRunners seems to log to the testrunner from VS and dotnet test.
So, the Exception or whatever the reason is for not running Test2 and Test3 will be swallowed, a level deeper. |
dotnet swallows silently xunit tests (maybe also test from other test frameworks) when there is a problem on the test discovery. I filed the same thing in the dotnet cli repo: https://github.com/dotnet/cli/issues/12187
Steps to reproduce
Checkout the repository https://github.com/DerAlbertCom/MisbehavingUnittestRunners run dotnet test. More details why the problem occurs is also there.
Expected behavior
At least the exception within the test discovery shows up. It would be better if it is possible to give more detail on exact type or test method.
Actual behavior
In the sample repository are 6 Unit Test, 2 of them get swallowed without any hint because of an exception within the test discovery on one test.
Environment data
The text was updated successfully, but these errors were encountered: