NUnit adapter for integrated test execution under Visual Studio 2012 (all updates), Visual Studio 2013 (all updates), and the Visual Studio 2015 Preview and CTPs. Compatible with NUnit 2.0 through 2.6.4.
Version 184.108.40.206 is broken! Do not update from version 220.127.116.11! I was helping someone with their new VS2013 installation when the only NUnit Adapter version available in the extensions was 18.104.22.168. He tried running our most recent project which worked under 22.214.171.124 and it complains about the "executor" not being found. I wanted to isolate the problem between his installation and mine found that my NUnit Adapter extension was requesting an update. I AM VERY SORRY THAT I DID THIS. As mine is broken exactly the same as his. I cannot run any tests using this adapter now. I read the bug reports and it appears everyone is having the same problem. I tried to roll mine back to version 126.96.36.199 but there is no way to do this! NO JOY
It works well but Test Explorer window presentation list is somewhat poor for me : I have many tests, and many test classes have a common base class. Some methods have the same name in several test classes.
So I have a display problem : when sorting by class, I see tests classes base class listed many times, then real classe listed, since they have a common base class the base class is listed every time.
When sorting by project, I see all homonyms methods one aside another. I see which file/class is concerned at bottom if I select an item.
I guess I have to complain to MS or maybe can you do something in your adapter to : a. fix class listing? (don't repeat base class in listing but list it once) b. see whether sorted by project items can display both test class and method names?
I installed the Version 3.4.0 from NuGet.
For Visial Studio 2013 and 2015 I have the message:
> Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.
For Visual Studio 2012 it works only with admin rights, because it writes the log-file in the Program Files (x86).
Getting error messages with test discovery failing for solutions with Debug|x86 for all projects
Exception NUnit.Engine.NUnitEngineException, Exception thrown discovering tests in ****.dll run tests in process - a 32 bit process is required.
In addition to upgrading the NUnit adapter from the nuget gallery I had also installed the ConcurrencyVisualizer plugin and GhostDoc plugin (both uninstalled now).
Also tried updating NUnit from 3.2.0 to 3.2.1 but did not help
Does Visual Studio Test Professional integrate well with NUnit? We are considering using it in combination with TFS, and were wondering if the test manager would also contain the unit testing written in NUnit?
in the release notes of the adapter it says: "Grouping by fixture is not yet available.in Visual Studio".
Well... I think with Update 3 or 4 VS 2012 included this grouping. However, it doesn't seem to work as intended. If I create subclasses, e.g.
<Test> Sub DoSth()
then the Test Explorer displays two tests in two groupings, and both groups are named "Parent". I'm pretty sure MSTest is doing this right, so I have to assume that the test adapter is reporting the test class names wrong for some reason.
Is this a known issue? And if so, is there a solution to it?
It appears this is still an issue in the 7/23/2015 2.0.0 release, if you subclass a test, the name of the base class shows in the VS  test explorer, not the name of the subclass, as would be expected.
Is there a place I should file a bug report?
Bugs are filed at https://github.com/nunit/nunit-vs-adapter/issues
We do have some issues with inheritance, there are a couple of issues on that already.
@Goppeltm raised this one, which in this particular case is: https://github.com/nunit/nunit-vs-adapter/issues/19
It requires changes to NUnit itself, and will be part of the 3.0 version
i included the NUnit Test Adapter as nuget Package in my TestProject.
Bunt when I run vstest.console.exe BuildTasks.Tests.csproj I get the following warning:
Warning: No test is available in the provided sources. Make sure that installed test discoverers & executors, platform & framework version settings are appropri ate and try again.
It works inside VS2015.
Am i missing something?
Thanks in advance
I am trying to run NUnit test from Test Explorer window but facing an error. I have installed NUnit adapter and can see all of my tests in the window. When I try to run the test which calls a web service hosted locally on my machine it throws the Impersonation error. (System.ArgumentException: Invalid token for impersonation - it cannot be duplicated). Please follow this link(http://tinyurl.com/kqgmkas) for more information.
Strangely the same test works and passes in the UnitTestExplorer window I opened from Resharper menu and also in NUnit GUI.
Is the NUnit Adapter for Visual studio compatible with VSTFS Test cases work items?
Currently I have a VSTFS 2012 and want to use NUnit to run Data Driven test cases.
The automated test cases are part of multiple Test plans in Microsoft Test Manager 2012 and will run as part of the Build deployment validation
Short answer: no, not yet. Long answer: MTM does not yet use the visual studio execution engine that was introduced in VS2012. Therefore, no test adapter will work in this environment. MTM still uses the old, overly complicated MS Test Adapter framework. So this is not an issue of NUnit, but rather that Microsoft has missed so far to migrate MTM to the new test runner / test adapter framework.
I'm receiving the message:
"No test is available in x:\Builds\6\146\Binaries\Web.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again."
We are running VS 2012 for the tfs build server. I just updated our customactivityrepo with the latest nunit vs test adapter libraries. I can run all tests from the build definition but when I try to set this filter "TestCategory=BVT" I receive the message above.
Any clue where I'm going wrong?
Cool I was able to get this Test Case Filter to work "Name=Test", still can't get TestCategory=BVT working.
I tried specifying this trait at the class level as well as the method level:
While installing I got an error this could not be installed because of .net framework not available.
1/30/2015 01:09:24 PM - Install Error : Microsoft.VisualStudio.ExtensionManager.MissingTargetFrameworkException: The extension 'NUnit Test Adapter' requires a version of the .NET Framework that is not installed.
This is because 2015 has been installed. Other VISX suffer from this too. WebEssentials VISX has solved this.
"Visual Studio 2015 performs an in place upgrade of .NET 4.5 to .NET 4.5.3. The extension.vsixmanifest, however, explicitly targets 4.5. Changing to [4.5,) resolves"