No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again

nunit make sure that test discoverer & executors are registered
xunit make sure that test discoverer & executors are registered
mstest make sure that test discoverer & executors are registered
no test is available in dll visual studio
no test matches the given testcase filter
no tests found to run.
nunit couldn't find any tests
the test source file provided was not found

I am in the process of upgrading our existing solution to .Net 4.6.1 and have been unable to get our unit tests to run during a server build. Locally they run as expected and flipping the framework version back to .Net 4.5.1 makes them run again on the server.

I am getting the following error:

No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

I have reproduced the problem in a simpler setup:

  • Solution with a single C# Unit Test project with two tests (one failing, one passing).
  • XAML build definition using the Default Template (TfvcTemplate.12.xaml)
  • TFS 2015 Update 1 XAML build server with Visual Studio Enterprise 2015 Update 1 installed (have six similar servers and all produce the same result)

You can try to change your default processor architecture in your Test Setting from X86 to X64. In my case this was the problem.

This happens if the platform target of your project under test is set to x64.

unit testing, Net 4.5.1 makes them run again on the server. I am getting the following error: No test found. Make sure that installed test discoverers & executors, platform  No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. I have reproduced the problem in a simpler setup: Solution with a single C# Unit Test project with two tests (one failing, one passing). XAML build definition using the Default Template (TfvcTemplate.12.xaml)

My build was not finding the tests either. My setup and solution for finding the tests are as follows.

I use VSTS (Visual Studio Team Services) and have a build that is configured to refresh the NUGET packages on every build. I am using NUnit and found that running the following NUGET command (from the package manager console in Visual Studio) to add NUnitTestAdapter library to my test project and the checking in the packages.config made the tests run in my VSTS build.

Install-Package NUnitTestAdapter

As Maurice mentions in the Comment to this post for NUnit3 use the following NUGET package (Look for other utils on the link. i.e: dotnet CLI and Paket CLI)

Install-Package NUnit3TestAdapter

Hope this helps.

No test is available () make sure that test discoverers & executors , I am in the process of upgrading our existing solution to .Net 4.6.1 and have been unable to get our unit tests to run during a server build. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again. visual studio 2017 version 15.7 windows 10.0 testing-tools Mike DePouw reported Jul 16, 2018 at 07:33 PM

In my case, had to:

1) convert test proj to netcore 2.0 (was netstandard 2.0)

2) add nuget package xunit.runner.visualstudio

Reference: http://www.neekgreen.com/2017/11/20/xunit-no-test-is-available/

No tests discovered · Issue #780 · microsoft/vstest · GitHub, make sure that test discoverers & executors are registered #554 I found this #​411 and followed your instructions and get something like this: Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again I tried few options in below solution, didn't work though. Solution-1

I got this error and was able to resolve it.

  1. I use Visual Studio Professional 2017
  2. In VS, I navigated to Tools --> Extensions And Updates
  3. At the top of the menu, I'd noticed that my NUnit adapter was disabled
  4. I clicked the [Enable] button
  5. I was able to initiate tests without errors.

Make sure that test discoverer & executors are registered and , 0\dbup-tests.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. Test  No test is available in E:\UnitTests\XFUITest\bin\Debug\Xamarin.UITest.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.

I'm using MSTest. For me, it was version missmatch and missing another dependent package-

1) My package folder contains only MSTest.TestFramework.1.2.1 package. In my project file(.csproj) the reference in Target Name was MSTest.TestAdapter.1.2.0 package which was not present in package folder. My packages.config has also reference of MSTest.TestFramework.1.2.0 .

2) So I installed MSTest.TestAdapter.1.2.0 from nuget package manager and align MSTest.TestFramework version to 1.2.0 in project and package file. Finally I add Microsoft.VisualStudio.TestPlatform.TestFramework and Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions in the reference.

Then everything was OK. Hope this help someone.

Build not detecting Unit Tests / Problems / Discussion Area , Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again. Closed - Not  No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. In my build definition I specify

What is needed at a minimum to have vstest.console to run using , They're just standard C# MS Unit tests, they get discovered in the Test Explorer Test.dll. Make sure that installed test discoverers & executors,  [6/4/2018 2:44:02 PM Warning] No test is available in C:\ihealautomatedTests\SeleniumTest\bin\x64\Debug\SeleniumTest.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.

https://social.msdn.microsoft.com/Forums/vstudio/e, Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. Well, I found this link, that helpedI didn't know that my visual studio project that has mstest installed as a package /vstestconsoleexe-not-discovering-any-of-the-tests?forum=vstest. No test is available in C:\Users\ben\proj\oss\DbUp\src\dbup-tests\bin\x64\Debug etcoreapp1.0\dbup-tests.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

Running unit tests in TFS/VSO Build vNext using xUnit adapter , Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. No results found to  *Warning: No test is available in .appx. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

Comments
  • According to Brian Harry from Microsoft, this is bug they are currently investigating. It should be fixed in Update 2, and a temporary workaround should be posted later. Source: link
  • I have the same problem for .Net 3.5 SP1 in Visual Studio 2013 Update 5.
  • @AndreyBushman: The error might be in 2013U5 too as it was released together with 2015RTM. But the workaround should work in your case too.
  • I had a similar problem, the workaround was simply in vs, under the test settings, to select the right default processer (32/64) bit, and no keep the engine runnig. (vs 2017.x)
  • This solved it for me. In my case, both the project being tested and the test project were set to x86. Tests were disoverable but failed to run. After I changed it to Any CPU, tests ran.
  • I'm also currently using VSTS. As adviced I added NUnit3TestAdapter (since I'm using NUnit 3.8.1) and this solution solved my problem. Thank you :-)
  • Install-Package NUnit3TestAdapter solved my issue :)
  • same issue was with me. I am using xunit with .net core
  • This also worked for me in Visual Studio 2017 with xunit and .NET Core 2.1.
  • in my case was a .net 4.6.1 project so the only thing missing was the xunit runner. Installed it and worked.
  • Yes! And don't forget to restart Visual Studio. That was required for me.
  • "At the top of the menu" what does that mean?
  • @SaiyajinGohan. After you complete step 2, the "Extensions and Updates" window appears. At the top of this window, I saw the NUnit adapter was disabled. Hope this clarifies....