I have reproduced this using a fresh VM with Windows 10 Pro. Steps to reproduce:
- Install Visual Studio 2015 Community Edition Update 3.
- Install CodeRush for Roslyn
- Clone Roslyn repo: https://github.com/dotnet/roslyn
- Run preliminary steps as per Roslyn documentation:
- Restore.cmd
- msbuild /v:m /m Roslyn.sln - Open Roslyn.sln in Visual Studio
- Click on the test tube icon next to any test and select "Run test"
Test started…
One or more errors occurred.
Summary: Passed: 0, Failed: 0, Ignored: 0
Duration: 51.5803
This hasn't happened in older versions of CodeRush for Roslyn.
Hi Alexei,
Thank you for letting us know about this problem.
I need some time to reproduce this problem locally. I will notify you as soon I will have results. Your patience is greatly appreciated.
Hi Alexei,
Thank you for your patience!
I have managed to reproduce this behavior locally. You will be notified when we prepare a fix for this problem.
Alexei,
We have made some changes, which allow you to run xUnit tests within the Microsoft Roslyn solution. I invite you to try this daily build that contains these changes:
DevExpress.CodeRush.Roslyn-16.1.6.16236.vsix
Unfortunately, there are still some groups of tests in Roslyn solution, which this CodeRush version cannot run, because this test contains an element that prevents them from running. We will continue working on these issues, and will prepare a fix shortly.
I'm experiencing the same issue (having the same setup - VS2015 Community Update 3, Win10Pro) on the following project:
https://github.com/ayende/ravendb (branch v3.5)
Also cannot run tests for the solution running on .NET Core (v4.0 branch):
https://github.com/ayende/ravendb/tree/v4.0
I've tried DevExpress.CodeRush.Roslyn-16.1.6.16236.vsix built but without success in running tests. In the past I was able to run test from v4.0 branch using the pre-release version of CodeRush for Roslyn.
I would appreciate if you could have a look into that.
Hi Arkadiusz,
Thank you for your comment.
We have checked both the v3.5 and v4.0 branches of the RavenDB project and tend to think that in both cases, problems with running tests have a different nature than the one discussed in this thread. So, I created a two separate tickets on your behalf and welcome you to continue discussion in the following threads:
1) Unable to run xUnit tests within a RavenDB v3.5 project
2) Unable to run xUnit tests within a RavenDB v4.0 project
Thank you!
Arkadiusz, you are always welcome!