-
Notifications
You must be signed in to change notification settings - Fork 325
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
Desktop test projects with class fixtures can fail to find tests. #408
Comments
@NTaylorMullen, the test discovery is failing because of following issue.
Finding these errors is quite hard currently, they are not showing up on stdout because of #300. Working on fixing it. |
@codito I see! I'm glad it's a duplicate bit then. Thanks!! |
@codito how did you get those logs? Having another issue similar to this and trying to find the underlying cause. |
@NTaylorMullen not sure if this is how @codito did it, but |
@natemcmaster nah, doesn't provide enough info 😢 . I was able to get the info needed by building source locally and updating my test host. Looks like they fixed this in newer builds |
@NTaylorMullen with #300 fixed, the issues from adapter have started showing up. Please update Test.Sdk reference to https://www.nuget.org/packages/Microsoft.NET.Test.Sdk/15.0.0-preview-20170210-02 to get the fix. |
Description
Running semi-complex test projects that utilize advanced class fixtures can result in tests failing to run. I've tried to repro this on smaller projects but to no avail. There's something unique about the MVC functional tests that trigger the issue. I've gone ahead and created a branch for bug investigation.
I was able to create a brand new test project with a single test that had the same csproj as the MVC functional tests and bring in the MvcTestFixture and use it to repro the issue.
Steps to reproduce
Expected behavior
Tests are run
Actual behavior
The text was updated successfully, but these errors were encountered: