NUnit Unit tests not showing in Test Explorer with Test Adapter installed

Question

I ve installed NUnit Test Adapter for VS2012   2013   When I first installed the Adapter tests were showing up  but they stopped showing up for some reason today   After building  rebuilding  cleaning  restarting  nothing shows up in Test Explorer   Why would this be happening   I m using VS2013 Ultimate

User · Accepted Answer

If your test project is set to target a 64bit platform  the tests won t show up in the NUnit Test Adapter

User · Answer

I had a working setup  for NUnit2 and NUnit3 depending on the solution  and multiple versions of Visual Studio between 2012 and 2017   and it suddenly stopped working one day  no tests detected in any solution or version of VS   In my case  it helped to delete  localappdata  Temp VisualStudioTestExplorerExtensions  After a restart of VS  everything worked as before

User · Answer

Check whether you have stated   TestFixureSetUp  and  Test   in the test class  sample   namespace ClassLibrary1      public class SimpleCalculator            public Calculator  calculator         TestFixtureSetUp        public void initialize                     calculator   new Calculator                   Test        public void DivideTest                    int a   10           int b   2           int expectedValue   a b           int actualValue    calculator Divide a  b            Assert AreEqual expectedValue  actualValue   Functionality not working properly

User · Answer

If you re using a NUnit3  version  there is a new Test Adapter available   Go to  Tools -  Extensions and Updates -  Online  and search for  NUnit3 Test Adapter  and then install

User · Answer

I had a similar issue where the tests where not being discovered  I had the correct version of NUnit  versions matched up between NUnit and adapter  and the tests where tagged correctly  I was running VS 2017 Enterprise not as an administrator  After starting VS as administrator the tests appeared

User · Answer

Just to add my   02 here  I ran into a similar issue just yesterday  where 168 of my tests were missing   I tried most everything in this post - most especially making sure my version s  of NUnit were the same - all to no avail   I then remembered that I had my tests divided into playlists  and these do not update automatically as you add new tests   So  when I deleted the playlists  BAM   all of my tests were back once more

User · Answer

My test assembly is 64-bit  From the menu bar at the top of visual studio 2012  I was able to select  Test  -   Test Settings  -   Default Processor Architecture  -   X64   After a  Rebuild Solution  from the  Build  menu  I was able to see all of my tests in test explorer  Hopefully this helps someone else in the future  D

User · Answer

I had some msbuild exe processes that were hung  I don t know if that was my problem or not  but it took me a lot of trail and error with reinstalling various NUnit adaptors before I found the hung processes

User · Answer

I also found that when I uninstalled nunit v3 2 1  the nunit framework reference for v3 2 1 was still in my project in solution explorer  Solution Explorer   ProjectName   References  If you right click it will show the version  Remove this Then Right click on References   Add Reference   Search for the version 2 x version and add then rebuild solution   That worked for me

User · Answer

I had this problem too but the cause was different   I m using VS2017 with F  4 0   Firstly  the console in Visual Studio does not give you enough details why the tests could not be found  it will just fail to the load the DLL with the tests   So use NUnit3console exe on the command line as this gives you more details   In my case  it was because the test adapter was looking for a newer version of the F  Core DLL  4 4 1 0   F  4 1  whereas I m still using 4 4 0 0  F  4 0    So I just added this to the app config of the test project -     lt dependentAssembly gt       lt assemblyIdentity name  FSharp Core  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt       lt bindingRedirect oldVersion  0 0 0 0-65535 65535 65535 65535  newVersion  4 4 0 0    gt     lt  dependentAssembly gt    i e  redirect to the earlier F  core

User · Answer

One other cause to this problem is if you open a project from a mapped drive - Visual Studio handles such projects properly  but apparently Nunit doesn t support them    Copying the project to a physical fixed the issue

User · Answer

I had the same problem  when suddenly any test didn t appeared on Test Explorer  window  I has the updated version of  NUnit3TestAdapter   and after lots of searches and efforts  I found that I need set the following values in project properties   In Solution Explorer window  right click on Project   Properties  Under Build tab  set Platform x64  and set Platform target x86 or Any CPU Build the project and all tests will be appear on Test Explorer  window   Important note  I came to a solution after seeing the next msg in the output window    Test run will use DLL s  built for framework Framework45 and platform X86  Following DLL s  will not be part of run   AutomationTests dll is built for Framework Framework45 and Platform X64

User · Answer

If you are using the TestCaseSource attribute  ensure the source exists and respects the documentation  otherwise your tests will not be discovered

User · Answer

Check for NUnit versions mismatch  The currently available NUnit Test Adapter only works for NUnit version 2 6 4 and below   To downgrade NUnit from version 3 x go to Package Manager Console   update-package NUnit -version 2 6 4  http   jeremybytes blogspot co ke 2015 11 review-of-unit-testing-makes-me-faster html

User · Answer

In my situation the  NUnit3 Test Adapter  has been disabled  To re-enable it go to menu  Tools- Extensions and Updates     On the left side select  Installed -  All    On the upper right corner search for  nunit    If you have  NUnit3 Test Adapter  installed  with the found item you can enable disable it

User · Answer

I started a new solution with a test project in it  and compared it against my original  problem project  The original  for some reason  had an app config in it  I excluded that file from the project and saw my tests reappear in the test explorer

User · Answer

This answer seems pretty basic but wasn t completely obvious to me at first  If you  re build the solution it only builds the projects that are configured to build in the Build - gt  Configuration Manager   This was my issue  I must have inadvertently changed a build configuration settings or something that caused my test projects not to build  when they previously were   So the Test Explorer window was looking at dlls that were out of date  It became clear to me this was the case after doing a Clean and seeing most of my tests disappear and not come back after a rebuild   further inspection of bin folder showed that these projects weren t being built at all

User · Answer

I experienced the problem mentioned by op  My case was that I was handed an old project and the tests were actually part of the system under test  I assume they were using the external test runner   this task chain resolved the issue for me    created a test project   moved the test files there  added references so the test project would compile  added the Nunit and Nunit adapter  NuGet packages to the test project recompiled   i was able to successfully run the Nunit tests

User · Answer

I use NUnit 3 and tried most of the other solutions I saw here  None of those worked for me   Even though already selected  reselecting the  quot Playlist  All Tests quot  option in test explorer showed all hidden tests in my case  I need to do this after every rebuild

User · Answer

I had to uninstall then re-install the xunit runner visualstudio nuget package   I tried this after trying all the above suggestions  so may be it was a mixture of things

User · Answer

If you are using VS 2017 and  net core  as said here  you should add references to the test framework NUnit 3 6 1  to the test runner NUnit3TestAdapter 3 8 0-alpha1 and to the test SDK Microsoft NET Test Sdk 15 0 0

User · Answer

Make sure your tests are properly marked with the Test attribute   If all of the tests are marked with only the Explicit attribute  the TestAdapter doesn t recognize the fixture

User · Answer

Tools NuGet Package Manager Manage NuGet Packages For Solution Browse NUnitTestAdapter WithFramework Ctrl R A to build run tests     Using NUnitTestAdapter WithFramework makes sure there are little no inconsistencies across versions of NUnit and NUnit Adapter  i e   it just works

[nunit] NUnit Unit tests not showing in Test Explorer with Test Adapter installed

Examples related to nunit