When I start a Live Unit Tests session on my solution in visual studio 2017, I get the following message:
No test adapters are referenced by this solution. If you have a test project, add a NuGet reference to a test adapter corresponding to the test framework used in order to run the tests. If you already have the required NuGet reference in your test project, performing a NuGet restore may resolve the issue.
What can I do to remedy this situation?
Test adapter used for unit tests. This adapter can be used to simulate sending messages from the user to the bot.
xunit.runner.visualstudio. This package contains the VSTest runner. This runner is capable of running . NET Framework projects from xUnit.net v1 and v2, and . NET Core and UWP projects projects from xUnit.net v2.
Automatic Integration Tests (made i NUnit) should be in a seperate project since they don't belong to any single project. But that means you cannot run tests on the Release build and few "heisenbugs" can fall through.
As the message implies, you need to install some NuGet packages, one for the testing framework and one for the visual studio test runner. If you are upgrading an old solution using MSTest, you first need to remove the reference to Microsoft.VisualStudio.QualityTools.UnitTestFramework
.
Then you need to open the Package Manager Console (under Tools-> Nuget Package Manager -> Package Manager Console). Select your unit test project(s) and run the following commands:
Install-Package MSTest.TestFramework
Install-Package MSTest.TestAdapter
If you are using a different test framework, such as XUnit or NUnit, you have to install either XUnit and xunit.runner.visualstudio, or NUnit and NUnit3TestAdapter
I created a brand new project in VisualStudio 2017 and was getting the same error message until I installed xunit.runner.visualstudio NuGet package. Follow these instructions on the Xunit getting started webpage (https://xunit.github.io/docs/getting-started/netfx/visual-studio)
I was able to see the tests in Test Explorer but they were being ignored.
I found and deleted a Local.testsettings file in the solution folder and it fixed the problem (I had earlier updated the nuget packages as the other answer suggests but that was not enough in my case).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With