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 220.127.116.11 is broken! Do not update from version 18.104.22.168! I was helping someone with their new VS2013 installation when the only NUnit Adapter version available in the extensions was 22.214.171.124. He tried running our most recent project which worked under 126.96.36.199 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 188.8.131.52 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?
Great plug in. I love being able to create test playlists now and isolate the tests to run to what I am working on. It seems a little slow to start up the tests but all the other aspects of this plugin make it well worth while.
Newer update on May 29th; The bug has been fixed with 0.95.1.1 version and everything works fine (you may need to uninstall and re-install the package) Quick turnaround. Thanks everyone, great extension to visual studio.
Update; The bug seems to be opened by others and a fix is on the way. Check the link below; https://bugs.launchpad.net/nunit-vs-adapter/+bug/1184231
Hello, I was very happy with the adapter but when I upgraded this morning (May 28th) to the beta 0.95 version, I can NO LONGER DEBUG the tests.
I have the following version for Visual Studio. Thanks for this great tool but is there a way to rollback to previous version until this issue is resolved. Sincerely, Baris Demir
Microsoft Visual Studio Premium 2012 Version 11.0.60315.01 Update 2 Microsoft .NET Framework Version 4.5.50709
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?
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?
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"
Is there any way to user EventListeners (http://nunit.org/index.php?p=eventListeners&r=2.6.3) with NUnit Test Adapter on Visual Studio 2012? I realize it can work with Nunit console without this
Please help me
When I run with "Run after build" on and change a test to make it fail and then build, the code builds and then the test discovery starts with the following log and the changed test is not run.
------ Discover test started ------
NUnit 184.108.40.206 discovering tests is started
NUnit 220.127.116.11 discovering test is finished
The specified type member 'Stale' is not supported in LINQ to Entities. Only initializers, entity members, and entity navigation properties are supported.
========== Discover test finished: 1869 found (0:00:01.3820795) ==========
My guess is something is going wrong with the nUnit adapter, thoughts?
I am running:
- VS2013 Update 3 (12.0.30723.00)
- nUnit Adapter 18.104.22.168
I have a NUnit test project that I'm trying to run on my TFS 2012 Build server. I'm getting the following error:
Exception System.InvalidOperationException, Exception thrown executing tests
No test is available in C:\Builds\1\Projects\NUNIT Test\bin\NUnitTestProject.dll C:\Builds\1\Projects\NUNIT Test\bin\NUnitTestProject.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.
I Have the NUnit.VisualStudio.TestAdapter 22.214.171.124 installed from NuGet and referenced in the project.
I also have set the Version control path to custom assemblies set on the controller, which contains (they basically are a copy of the NuGet package):
For test purposes, I'm only building the NUnit test project.
My test class is very simple and is the following:
public class MySuperTests
public void MyFirstUnitTestMethod_ReturnsTrue()
Is there something I haven't done correctly?
The problem I believe lies in the 1.1.X.X version.
Updating to 126.96.36.199 I did not have the exception anymore, however, I did have the tests not found problem.
There are some issues going on about that on github https://github.com/nunit/nunit-vs-adapter/
Is there any word on when the 188.8.131.52 version will make it to NuGet? I understand that I can download 184.108.40.206 vsix manually, but that won't really help on the build server, where I'm counting on NuGet to keep things up to date. I don't see 220.127.116.11 even when I allow PreRelease, and I do not have the required rights to install the vsix on the build server. So what am I supposed to do?