Problems with .NET unit testing

JetBrains Rider automatically detects unit tests and provides a unit test runner to run and debug them. We are continuously improving unit testing with JetBrains Rider, but there are still some areas which are not supported.

So what is currently supported and what is not?

Supported since 2017.2

If you experience any issues with a supported unit testing framework on a supported runtime, create a request and describe the problem in detail, as it will help to sort it out timely.

Essential information is to determine the cause of the issue

Environment

1. OS version, for example, Windows 10 or Mac OS X 10.8
2. JetBrains Rider version: Help -> About
3. Unit testing framework version, for example, xUnit 2.2.0
4. MSBuild version: Settings -> Build, Execution, Deployment -> Toolset and Build (find screenshot below)
5. .NET Core version in case you have .NET Core project:
   • Check a path to dotnet executable via Settings -> Build, Execution, Deployment -> Toolset and Build (find screenshot below)
   • Go to the directory with dotnet executable via terminal
   • Run "dotnet --version" command

Log Files

1. Build your solution and then collect Rider logs: Help -> Collect Logs
2. Run Unit Tests if you can see them in the unit test explorer
   • Get launch log files: Launch settings -> Show Last Launch Log (find screenshot below) or click on gear icon -> Diagnostics -> Show Last Launch Log
   • Get unit test process log files as described here
3. Attach the logs to the request

Additional information

1. Sample solution where the issue reproduces is very much appreciated
2. Can you see your unit tests in unit test explorer?
3. Are there any steps to reproduce the issue?
4. Has it worked in the previous version of JetBrains Rider?