CODEWITHSUNDEEP
c#visual-studiovisual-studio-2017nunit
Helen Araya
Helen Araya

Reputation: 1936

VS2017 and NUnit 3.9 No test is available

I am using the latest VS2017 version 15.6.4, NUnit3TestAdapter 3.10.0 and Nunit version 3.9.0.0.

When I try to run a unit test in Test Explorer the test are grayed out, when I right click and and run selected tests I see the following error: No test is available Here is how my test class looks

    [TestFixture]
    public partial class ListViewBOTest
    {
    [Test]
     public void TestSearch_DateTime()
      {
        Assert.AreEqual(1,0);
      }

    }

Here is a screenshot of my tests

Text from output:

[3/26/2018 10:53:55 AM Informational] ------ Run test started ------
[3/26/2018 10:53:55 AM Informational] NUnit Adapter 3.10.0.21: Test execution started
[3/26/2018 10:53:55 AM Informational] Running all tests in C:\Projects\MVPPlant\DEV\CMMSdg.Plant\CMMSdg.Plant\Sln.2010\CMMSdg.Plant.BusinessObjects.Test\bin\Debug\CMMSdg.Plant.BusinessObjects.Test.dll
[3/26/2018 10:53:56 AM Informational] NUnit failed to load C:\Projects\MVPPlant\DEV\CMMSdg.Plant\CMMSdg.Plant\Sln.2010\CMMSdg.Plant.BusinessObjects.Test\bin\Debug\CMMSdg.Plant.BusinessObjects.Test.dll
[3/26/2018 10:53:56 AM Informational] NUnit Adapter 3.10.0.21: Test execution complete
[3/26/2018 10:53:56 AM Warning] No test is available in C:\Projects\MVPPlant\DEV\CMMSdg.Plant\CMMSdg.Plant\Sln.2010\CMMSdg.Plant.BusinessObjects.Test\bin\Debug\CMMSdg.Plant.BusinessObjects.Test.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
[3/26/2018 10:53:56 AM Informational] ========== Run test finished: 0 run (0:00:01.0435303) ==========

Upvotes: 26

Views: 20220

Answers (14)

M-A Charlotte
M-A Charlotte

Reputation: 363

I had the same issue, but it was fixed after installing "NUnit 3 TestAdapter version 3.16.1" via NuGet to my project.

Upvotes: 0

atul parate
atul parate

Reputation: 780

I have also encountered the same issue.

Steps to resolve this issue - 

 1. Install/Reinstall NUnit3TestAdapter package
 2. Delete Debug folder from the Bin
 3. Clean --> Build the project

Note - Also ensure all the packages are installed properly.

Now try to execute the tests.

Upvotes: 0

MrTesla
MrTesla

Reputation: 99

This is caused due to memory problem.

  • Clean object after test execution

Sample Code

private TestController testController;

[OneTimeSetUp]

public void TestSetup()

{

testController= new TestController();

}



[OneTimeTearDown]

public void TestCleanup()

{

testController= null;

}
  • Change test execution to 64 bits in settings

Test -> Test Settings -> Default Processors Architecture -> x64.

Upvotes: 0

Joakim M. H.
Joakim M. H.

Reputation: 470

What worked for me was to delete the ComponentModelCache folder located at %localappdata%\Microsoft\VisualStudio\<version>

Upvotes: 1

Rob Powell
Rob Powell

Reputation: 1387

Had the same problem. In my case I found that the NUnit test adapter will not be used by Test Explorer if your test project contains a reference to MSTest. Typically the Microsoft.VisualStudio.TestPlatform.TestFramework.dll but also check your .csproj file for "MSTest" and your packages.config file.

I discovered this by first enabling diagnostic logging for Visual Studio tests. This is found under "Tools" -> "Options" -> "Tests" -> "Logging Level".

In my log I found this entry:

[22/11/2018 10:36:42 Diagnostic] Project C:\Git\myProject\src\myProject.Tests\myProject.Tests.csproj references test adapter: MSTest.TestAdapter, version 1.1.18

Upvotes: 0

Alexander Razvalinov
Alexander Razvalinov

Reputation: 69

After installing NUnit through nuget tests have appeared into Test Explorer but when I ran them I got "No test is available". Installing NUnit Test Adapter fixed the issue.

Upvotes: 2

Phil
Phil

Reputation: 77

The messages in the Test Output window ("NUnit failed to load [assembly]", "No test is available...", etc.) can hide the underlying issue that's causing the runner to not load the test assembly. This includes hiding failures to load dependencies of the test assembly or the item under test.

If there's a test assembly that's showing up in the Test Explorer window, but the tests refuse to run, it's worth temporarily enabling fusion logging to see if any assembly binding errors occur when trying to run the tests.

Upvotes: 2

AGR
AGR

Reputation: 351

I had similar problem when using Xamarin.Forms. The solution was to install NUnit.XForms from NuGet and add

<PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.3.0" />

to csproj file of the project where the tests are.

Upvotes: 1

Peter Morris
Peter Morris

Reputation: 23224

Make sure you have installed the NUnit3 Test Adapter from here

https://marketplace.visualstudio.com/items?itemName=NUnitDevelopers.NUnit3TestAdapter

Upvotes: 44

Cubelaster
Cubelaster

Reputation: 342

I had the same problem as Amete Blessed and commenting out other Test methods made Test Explorer work and run my test

Upvotes: 2

Erik McCarty
Erik McCarty

Reputation: 21

I found that my Build Events were wrong. Invalid copy command blew all my tests and half a day:

Copy C:\repo\Architecture\*.json $(ProjectPath)/Y
Copy C:\repo\Architecture\*.json $(TargetPath) /Y

instead of 

Copy C:\repo\Architecture\*.json $(ProjectDir)/Y
Copy C:\repo\Architecture\*.json $(TargetDir) /Y

Upvotes: 2

hem
hem

Reputation: 2270

Can you check the following steps and see if it works?

  1. In the Visual Studio menu, go to Test > Test Settings > Default Processor Architecture and make a note if X86 is selected or X64
  2. Now go to the Build section in the Properties window of the project where the tests are written. Make sure the Platform target drop-down is selected to either Any CPU or at least it matches the architecture from the above step 1.

Now if you build the solution and try running those tests, you should see that they are now running.

Upvotes: 17

Nick Booth
Nick Booth

Reputation: 1

Rather than using the Test Explorer, can you right click on the solution and Run Unit Tests from there?

Upvotes: 0

Nick DeVore
Nick DeVore

Reputation: 10166

You may have been a casualty of this problem that was (theoretically) resolved in 15.6.3. According to this answer, try deleting your %temp%\VisualStudioTestExplorerExtensions folder. That has resolved the issue for some other users.

Upvotes: 0

Related Questions