Hello, I've been trying to enable a good size project to use the NUnit Test Adapter under TFS Build (0.96).

Some of the tests have been hanging on the build machine. I've not been able to see anything useful from the NUnit Test Adapter in the vstest logs that we turned on to try to diagnose the problem. The adapter also appears not to be aware of the timeout information in the .testsettings file passed to vstest so the build agent gets wedged.

There are notes on enabling UTE logging here:

http://blogs.msdn.com/b/aseemb/archive/2012/03/02/how-to-enable-ute-logs.aspx

Could you consider instrumenting the adapter to report progress, perhaps along the lines of:

using Microsoft.VisualStudio.TestPlatform.ObjectModel;

...

    public void RunStarted(string name, int testCount)
    {
        testLog.SendMessage(TestMessageLevel.Informational, "Run started: "+name);
        if (EqtTrace.IsVerboseEnabled)
        {
            EqtTrace.Verbose("Run started: "+name);
        }
    }

Hopefully this makes sense. I'm not overly familiar with the test adapter APIs, the author of the blog post on UTE logs advised on the EqtTrace API privately.

Moved from https://bugs.launchpad.net/nunit-vs-adapter/+bug/1199814

We've got tests that load DLLs dynamically, and the shadow copy mechanism within NUnit fails to copy these DLLs to the temporary directory where the test are run from.

The simple work around we've been using in NUnit (as well as Reshaprer's NUinit runner) is to disable shadow copy in the options.

The NUnit Test Adapter for Visual Studio doesn't allow us to disable Shadow Copy and therefore prevents our use of NUnit within Visual Studio 2012.

Could you add the ability to disable Shadow Copy to the adapter?

See discussion at https://bugs.launchpad.net/nunit-vs-adapter/+bug/1084284

I have written an addin which allows me to write field tests instead of tests being methods. I can navigate to where the assertions failed just fine due to console output and stack traces, but there is no source information available for passed tests or failures (in the way NUnit supplies). I believe the issue may be here: http://bazaar.launchpad.net/~nunit-vs-team/nunit-vs-adapter/trunk/view/head:/src/NUnitTestAdapter/NavigationData.cs

It calls:

var method = definingType.GetMethod(methodName);
if (method == null) return null;

Which will always return null for my tests. Would changing the call to definingType.GetMember work to support both methods and fields?

What about creating another function which can locate non-methods tests?

From https://bugs.launchpad.net/nunit-vs-adapter/+bug/1177434

When running async tests in visual studio the source is not visible when double clicking on the test. Also code coverage is not working for async tests. Also async tests take an extremely long time to run like 15+ seconds even though the execution time shows a very short time like 1ms.

See discussion at https://bugs.launchpad.net/nunit-vs-adapter/+bug/1221947

From https://bugs.launchpad.net/nunit-vs-adapter/+bug/1065462 which includes some discussion.

See nunit/nunit#59 for the underlying NUnit issue.

Moved from nunit/nunit#116
See details there.

Tested with NUnit Test Adapter V1.0

Visual Studio 2012 also introduced a new command line for the test engine called vstest.console
(see also http://msdn.microsoft.com/en-us/library/vstudio/jj155796.aspx)

With this, it is possible to automate Test runs. Without any additional parameters, it executes all the tests, which works perfectly fine with NUnit projects as well. It has two main options to filter tests: the first one "tests" filters via the fully qualified name, and works perfectly well with the Nunit Test Adapter.
The second one is called "TestCaseFilter", and currently accepts four attributes to filter from: FullyQualifiedName, TestCategory, Priority and Owner
(see here: http://blogs.msdn.com/b/vikramagrawal/archive/2012/07/23/running-selective-unit-tests-in-vs-2012-rc-using-testcasefilter.aspx)

Although obviously not all of these properties are useful for NUnit, it would be very nice if at least FullyQualifiedName and TestCategory were mapped accordingly.

Visual studio throws an exception while discovering tests.

NUnit 1.0.0.0 discovering tests is started
Exception thrown discovering tests in ****
System.TypeLoadException: Could not load type 'System.Record' from assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Where mscorlib is
Script# Core Assembly
ScriptSharp.0.7.5.1\tools\mscorlib.dll
version 0.7.0.0

I get a bunch of ArgumentExceptions when debugging nunit tests (64bit)

It seems The Nunit test adapter event listener is passing null, empty or blank string message to the microsoft logger proxy's sendmessage method.

e.g.
A first chance exception of type 'System.ArgumentException' occurred in Microsoft.VisualStudio.TestPlatform.Core.dll
A first chance exception of type 'System.ArgumentException' occurred in mscorlib.dll
A first chance exception of type 'System.ArgumentException' occurred in Microsoft.VisualStudio.TestPlatform.Core.dll
A first chance exception of type 'System.ArgumentException' occurred in mscorlib.dll

Here's the stack trace:

Microsoft.VisualStudio.TestPlatform.Core.dll!Microsoft.VisualStudio.TestPlatform.Core.Logging.TestRunMessageLoggerProxy.SendMessage(Microsoft.VisualStudio.TestPlatform.ObjectModel.Logging.TestMessageLevel testMessageLevel, string message) + 0xa0 bytes
NUnit.VisualStudio.TestAdapter.dll!NUnit.VisualStudio.TestAdapter.NUnitEventListener.TestOutput(NUnit.Core.TestOutput testOutput) + 0x1e8 bytes
[Native to Managed Transition]
[Managed to Native Transition]
mscorlib.dll!System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage msg) + 0x405 bytes
mscorlib.dll!System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage reqMsg) + 0xc8 bytes
mscorlib.dll!System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage reqMsg) + 0x16c bytes
mscorlib.dll!System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(object[] args) + 0xce bytes
[Native to Managed Transition]
[Managed to Native Transition]
mscorlib.dll!System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage reqMsg) + 0x113 bytes
mscorlib.dll!System.Runtime.Remoting.Channels.ChannelServices.SyncDispatchMessage(System.Runtime.Remoting.Messaging.IMessage msg) + 0x158 bytes
mscorlib.dll!System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(byte[] reqStmBuff, System.Runtime.Remoting.Messaging.SmuggledMethodCallMessage smuggledMcm, out System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage smuggledMrm) + 0xaa bytes
mscorlib.dll!System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatchCallback(object[] args) + 0x92 bytes
[Appdomain Transition]
mscorlib.dll!System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatch(byte[] reqStmBuff, System.Runtime.Remoting.Messaging.SmuggledMethodCallMessage smuggledMcm, out System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage smuggledMrm) + 0xa0 bytes
mscorlib.dll!System.Runtime.Remoting.Channels.CrossAppDomainSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage reqMsg) + 0x15d bytes
mscorlib.dll!System.Runtime.Remoting.Proxies.RemotingProxy.CallProcessMessage(System.Runtime.Remoting.Messaging.IMessageSink ms, System.Runtime.Remoting.Messaging.IMessage reqMsg, System.Runtime.Remoting.Contexts.ArrayWithSize proxySinks, System.Threading.Thread currentThread, System.Runtime.Remoting.Contexts.Context currentContext, bool bSkippingContextChain) + 0x8c bytes
mscorlib.dll!System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvoke(System.Runtime.Remoting.Messaging.IMethodCallMessage reqMcmMsg, bool useDispatchMessage, int callType) + 0x22c bytes
mscorlib.dll!System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(ref System.Runtime.Remoting.Proxies.MessageData msgData, int type) + 0x1f4 bytes
nunit.core.dll!NUnit.Core.OutputEvent.Send(NUnit.Core.EventListener listener) + 0x52 bytes
nunit.core.dll!NUnit.Core.EventPump.PumpThreadProc() + 0xf3 bytes
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) + 0x285 bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) + 0x9 bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x57 bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x51 bytes
[Native to Managed Transition]
[Appdomain Transition]
[Native to Managed Transition]

Another small issue with the TestCaseFilter. I guess I am missing some character escape mechanism, but because I can't find any documentation for it I open this issue.

When executing tests via the vstest.console api, it seems like expressions containing brackets are ignored.
Let's imagine the following test class:

<TestFixture("Alpha", "Alpha")>
<TestFixture("Alpha", "Beta")>
<TestFixture("Beta", "Alpha")>
<TestFixture("Beta", "Beta")>
Class FixtureParameterExampleA

    Sub New(arg As String, arg2 As String)

    End Sub

    <Test>
    Sub DoExample()

    End Sub

End Class

<TestFixture("Alpha", "Alpha")>
<TestFixture("Alpha", "Beta")>
<TestFixture("Beta", "Alpha")>
<TestFixture("Beta", "Beta")>
Class FixtureParameterExampleB

    Sub New(arg As String, arg2 As String)

    End Sub

    <Test>
    Sub DoOtherExample()

    End Sub
End Class

now I want to start them via console. I launch vstest.console (developer command prompt makes this easier) like this:

vstest.console "D:\ExampleTestContainer.dll" /usevsixextensions:true /TestCaseFilter:FullyQualifiedName~FixtureParameterExampleB

So far so good, this results in 4 successful tests.
Now, what I would like to do is run only tests from class B which first parameter is "Alpha". I would expect something like this to work:

vstest.console "D:\ExampleTestContainer.dll" /usevsixextensions:true /TestCaseFilter:FullyQualifiedName~FixtureParameterExampleB("Alpha"

This results in zero tests. After a little trial & error I learned that quotation marks need to be escaped by double quotation mark (I guess due to the commandline), and commas are actually allowed, so in fact a valid solution would be:

vstest.console "D:\ExampleTestContainer.dll" /usevsixextensions:true "/TestCaseFilter:FullyQualifiedName~ExampleB&FullyQualifiedName~""Alpha"","

This executes exactly two tests.
But as soon as the brackets are involved you get no results:

vstest.console "D:\ExampleTestContainer.dll" /usevsixextensions:true "/TestCaseFilter:FullyQualifiedName~("

I guess that the brackets are escaped too, somehow, but I was unable to find out how.

Why are we doing this, anyway? We are trying to wire our tests to our build system, or to be more precise: to our test management. For this we need filter queries, because we usually don't want to assign all unit tests in a project to a single requirement.

Test Explorer only shows one test, given the following method.

    [TestCase(5, new int[] { 2, 3 })]
    [TestCase(5, new int[] { 1, 2, 2 })]
    public void Class1Test(int expectedTotal, int[] vals)
    {
        var calc = new Calculator();
        int total = calc.AddNums(vals);
        Assert.AreEqual(expectedTotal, total);
    }

Changing the first int in one of the test cases causes Explorer to show two test:

    [TestCase(5, new int[] { 2, 3 })]
    [TestCase(6, new int[] { 1, 2, 2 })]
    public void Class1Test(int expectedTotal, int[] vals)
    {
        var calc = new Calculator();
        int total = calc.AddNums(vals);
        Assert.AreEqual(expectedTotal, total);
    }

Used "install-package NUnitTestAdapter.WithFramework" to install version 0.96 on Visual Studio 2012 Update 3.

NUnit gui shows two test in both of the above scenarios.

For more info see https://bugs.launchpad.net/nunit-vs-adapter/+bug/1207946

Tests implemented in files that are not in projects root folder do not apear in Test Explorer window and are not runned during "run all" nor durng "run tests" from context menu of the file containing tests.

See discussion at https://bugs.launchpad.net/nunit-vs-adapter/+bug/1074130

We have some integration tests that can take longer than 2 minutes on our TFS build machine. These are not reported by the test runner.
I have confirmed that this also occurs in VS 2012 Update 2.
It looks like any test that takes longer than 180 seconds is not reported!
Try the below test fixture. Tests "Quick" and "Slow" will be executed and reported; test "Slower" does not appear to even execute, and is shown as 'dimmed' in the Test Explorer window.
Note that all 3 tests will run and get correctly reported by NUnit Console.

[TestFixture]
public class TimeoutTest
{
    [Test]
    public void Quick()
    {
        Thread.Sleep(1);
    }

    [Test]
    public void Slow()
    {
        Thread.Sleep(150000);
    }

    [Test]
    public void Slower()
    {
        Thread.Sleep(250000);
    }
}

Using NodeUnit0.86 with VS2012 Update4 and the NodeUnit VS plugin.

If a test case contains a // style comment, the test runs in the console but results in:
"Test adapter sent back a result for an unknown test case. Ignoring result for 'aTestCase'."

The test itself doesn't show up in the test explorer. All others are ok.
(This might be an issue in NodeUnit itself)

Test to replicate:
put the following into any working file of test cases...

exports.aTestCase = function(test) {
test.ok(true, "This should always pass.");
//a comment
test.done();
};

exports.aTestCase.meta = { traits: ["Sample Test", "Sample Trait"], description: "This test should always pass." };

Any use of Random, including our RandomAttribute, in the generation of a test case causes the test to be listed as not run in the TestExplorer window. The same tests run as expected in the NUnit runners.

See https://bugs.launchpad.net/nunit-vs-adapter/+bug/1242315 for more info.

If you have a generic fixture and try running or debugging a single test by right clicking it in code and selecting 'Run Tests' or 'Debug Tests' it instead runs all tests in the code file. Doing the same for a non generic fixture correctly runs just the single test.

Referring to the example below, the tests NonGenericTest1 and NonGenericTest2 can be run independently, but attempting to run either GenericTest1 or GenericTest2 results in all four being run. Ideally it should run just the selected test for each of the generic types specified.

[TestFixture(typeof(int))]
public class GenericTests<T>
{
    [Test]
    public void GenericTest1()
    {
    }

    [Test]
    public void GenericTest2()
    {
    }
}

[TestFixture]
public class NonGenericTests
{
    [Test]
    public void NonGenericTest1()
    {
    }

    [Test]
    public void NonGenericTest2()
    {
    }
}

--> Moving to NUnit Framework

It's definitely more a feature request than a bug... but nonetheless:

I have a TestCaseSource that returns a collection of XElements, i.e. XML nodes. Because by default the test case generation calls ToString on each parameter, the final test name looks quite ugly:
DoSth(") ... or worse

So, to overwrite this behaviour I thought I'd encapsulate my data in TestCaseData:
new TestCaseData(myXElement).SetName(myXElement.@myAttribute)
However, this not only overwrites the argument, but the whole name, including the method name:
myTestCaseName

So all tests that reference this TestCaseSource end up with the same set of names. This is ugly, because obviously each test is defined via its test data AND its test behaviour.

If I could imitate the original test name layout, this would be no problem. But the TestContext isn't set when reading the TestCaseSource.
So my guess is: the test case generator uses some algorithm to create the test name, and TestCaseData.SetName breaks this behaviour.

So, it would be nice if either .SetName would be handled the same way as the default .ToString implementation, or if the test case name creation would be customizable somehow.

The page instructs people to add bugs to launchpad. Should be corrected to point to github
Update info on versions supported in existing versions.
Info for 2.6.2 is latest now.
Info for 2.6.3 is older info.

The title about explains it. I reference MVC 5 and the tests no longer appear. I change the reference to MVC 4 (via NuGet) and it works, with all other settings exactly the same.

I am using the vs adapter 1.0.0.0, VS 2012 Professional, and .NET framework 4.5 in the test project.

I also tried loading the test project in the GUI, but get the exception:

Test load failed!

System.IO.FileNotFoundException : Could not load file or assembly 'MyProject.Tests, Version 4.0.0, Culture=neutral, PublicKeyToken=1923abe4657913cc' or one of its dependencies. The system cannot find the file specified.

Stack Trace:

System.IO.FileNotFoundException...

Server stack trace: 
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.UnitySerializationHolder.GetRealObject(StreamingContext context)
   at System.Runtime.Serialization.ObjectManager.ResolveObjectReference(ObjectHolder holder)
   at System.Runtime.Serialization.ObjectManager.DoFixups()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.DeserializeObject(MemoryStream stm)
   at System.Runtime.Remoting.Messaging.SmuggledMethodReturnMessage.FixupForNewAppDomain()
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.SyncProcessMessage(IMessage reqMsg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at NUnit.Core.TestRunner.Load(TestPackage package)
   at NUnit.Util.TestDomain.Load(TestPackage package)
   at NUnit.Core.ProxyTestRunner.Load(TestPackage package)
   at NUnit.Util.RemoteTestAgent.AgentRunner.Load(TestPackage package)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [1]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at NUnit.Core.TestRunner.Load(TestPackage package)
   at NUnit.Core.ProxyTestRunner.Load(TestPackage package)
   at NUnit.Util.ProcessRunner.Load(TestPackage package)
   at NUnit.Util.TestLoader.LoadTest(String testName)

We'll need to determine where to run this. Since it's VS-dependent, we may need to put it on team server.

I'd like to help fix #22. I have not debugged a visual studio extension before. I understand that there is a way to run Visual Studio itself under the debugger, with the debug build of the extension. However, trying to debug the NUnitTestAdapter project does not work - there are no debug settings configured.

Could you please add a brief README (or just add to this issue) that explains how to get started?

On another note, I ran the unit tests from the Master branch and 24 tests failed (69 passed.) Is this expected?

I am using NUnit and the NUnit Test Adapter to run unit tests in Visual Studio 2013. The test project is managed C++ that is testing native C++.

Breakpoints in the test project are hit as expected, but I can not step into production code (native C++) and native tests do not trigger breakpoints.

Switching to MSTest allows these breakpoints to be hit.

This will be a first, rough cut of running NUnit tests from an adapter that supports 3.0.

Only 3.0 will be supported, pre-3.0 tests will be ignored.
The adapter name will be different from the existing adapter, allowing both to be installed.

The 2 tests below are identical except for the space after the word function.
The first won't be discovered (but will show as run on the output)
The second is fine

exports.hiddenTest= function(test) {
test.equal("test0", "test0");
test.done();

};exports.visibleTest= function (test) {
test.equal("test0", "test0");
test.done();
};

We are having problem with the test adapter in our TFS build environment. Here are the versions used:

• NUnit version 2.6.2
• NUnit test adapter version 0.96.0.4
• Visual Studio 2012 update 3
• TFS 2012 update 1

Here are the steps to reproduce:

• Create a .NET 3.5 class library project with at lease one NUNit test. In this example it is called "aaa.bbb.Tests.dll"
• Configure your build environment according to this guide: http://www.mytechfinds.com/articles/software-testing/6-test-automation/72-running-nunit-tests-from-team-foundation-server-2012-continuous-integration-build

Basically you copy the test adapter assemblies to a folder reachable by the build controller and edit the "test assembly file specification" in the build definition to match the name of your NUNit test project.

• Queue a build, and wait for it to finish.

Result: You should see correct test results in the build report.

However, the folder specified in "version control path to custom assemblies", where the test adapter assemblies are copied, is used for more than just test adapters. For example you place assemblies that contains workflow activities for customized build workflows. And here comes the strange part:

• Create a new .NET 4.0 class library project in visual studio. Name it something that comes before "nunit" in the alphabet, for example "abc.dll". In our case it contains workflow activities, but we can reproduce the problem with just the the standard "Class1.cs".
• Build the .NET 4.0 project and check in the resulting "abc.dll" to the "version control path to custom assemblies" folder. That is the same folder as the NUNit test adapter assemblies were copied earlier.
• Queue another build.

Result: No tests are run and the build report says:

Assembly not supported: C:\Builds\5\aaa\bbb\bin\aaa.bbb.Tests.dll
No test is available in C:\Builds\5\aaa\bbb\bin\aaa.bbb.Tests.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

We have found the following ways to make it work again:

• Remove the "abc.dll" from the custom assemblies folder.
• Rename "abc.dll" to "xyz.dll" (!)
• Change the target framework version of "abc.dll" to .NET 3.5.

We can also reproduce the problem locally in Visual Studio, using the same project setup as above. This is a strange thing to do, but much easier for troubleshooting.

• Install the latest NUnit test adapter for Visual Studio.
• Open the .NET 3.5 class library project containing NUnit tests.
• Open the Test Explorer window and build the project. Your tests should appear.
• Right click some of the tests and select "Run selected tests".

Result: Your tests should run successfully.

Now look up the Visual Studio extensions folder, where the test adapter is installed. On my computer it is C:\Users\username\AppData\Local\Microsoft\VisualStudio\11.0\Extensions\do0tbn4e.opv.

• Copy the "abc.dll" to the test adapter folder you found above.
• Restart Visual Studio, open and build the NUnit project

Result: The tests are discovered in the Test Explorer window as before, but when you right click a test and select "Run selected tests" you get the following error message in Output/Tests:

NUnit 0.96.0.4 executing tests is started
Assembly not supported: c:\Projects\aaa\bbb\bin\Debug\aaa.bbb.Tests.dll
NUnit 0.96.0.4 executing tests is finished

We find it very strange that an unreferenced .NET 4.0 assembly in the same folder as the test adapter can disturb the test execution. And we have really no choice to alter our .NET versions. The NUnit test projects need to be 3.5 for legacy reasons and the workflow activity assemblies needs to be .NET 4.0, or actually .NET 4.5, to reference the TFS 2012 assemblies.

More discussion at https://bugs.launchpad.net/nunit-vs-adapter/+bug/1209192

For debugging of my test I write 500000 lines (26 character per line) to the output.
In the NUnit executable I can execute the test and view it's output.
Though in Visual Studio it will cause VS to completely crash when I click to open the Output of the test.

Note: In VS I can open the Output of other tests.

Configuration:
Visual Studio 2013 (Version 12.0.30110.00 Update 1)
NUnit (Version 2.6.3.13283)
NUnit Test Adapter (Version 1.0.0.0)

I have a NUnit test marked with the following:
[Category("TFSFriendly")]

In TFS build definition I have the following value for Test Case Filter:
TestCategory=TFSFriendly

I would expect that this would result in only my one test being run during TFS Build. However, no tests are run. I know that other settings related to tests and all other configuration are okay because if I remove the filter, all of my tests run.

I am using version 1.0 of NUnit Test Adapter. TFS version is 2012 Update 2.

From https://bugs.launchpad.net/nunit-vs-adapter/+bug/1240704

The ShadowCopy registry setting is named UseShallowCopy which is wrong. See https://github.com/nunit/nunit-vs-adapter/wiki/Tips-And-Tricks

The VS test adapter seems to choke on MonoTouch libraries in the solution:

------ Discover test started ------
NUnit 1.0.0.0 discovering tests is started
Dependent Assembly monotouch, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065 of C:\Users\Oren\Source\Main\Core.iOS.Tests\bin\iPhoneSimulator\Debug\CoreiOSTests.exe not found. Can be ignored if not a NUnit project.
Exception thrown discovering tests in C:\Users\Oren\Source\Main\Core.iOS.dll
System.IO.FileLoadException: Could not load file or assembly 'System.Reactive.Core, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
File name: 'System.Reactive.Core, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Server stack trace:
at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
at System.Reflection.RuntimeAssembly.GetExportedTypes()
at NUnit.Core.CoreExtensions.InstallAdhocExtensions(Assembly assembly)
at NUnit.Core.Builders.TestAssemblyBuilder.Load(String path)
at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, Boolean autoSuites)
at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, String testName, Boolean autoSuites)
at NUnit.Core.TestSuiteBuilder.BuildSingleAssembly(TestPackage package)
at NUnit.Core.TestSuiteBuilder.Build(TestPackage package)
at NUnit.Core.SimpleTestRunner.Load(TestPackage package)
at NUnit.Core.ProxyTestRunner.Load(TestPackage package)
at NUnit.Core.ProxyTestRunner.Load(TestPackage package)
at NUnit.Core.RemoteTestRunner.Load(TestPackage package)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at NUnit.Core.TestRunner.Load(TestPackage package)
at NUnit.Util.TestDomain.Load(TestPackage package)
at NUnit.VisualStudio.TestAdapter.NUnitTestDiscoverer.DiscoverTests(IEnumerable`1 sources, IDiscoveryContext discoveryContext, IMessageLogger messageLogger, ITestCaseDiscoverySink discoverySink)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value HKLM\Software\Microsoft\Fusion!EnableLog to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Dependent Assembly monotouch, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065 of C:\Users\Oren\Source\Main\iOS.Agent\bin\iPhoneSimulator\Debug\iOS_Agent.exe not found. Can be ignored if not a NUnit project.
Dependent Assembly monotouch, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065 of C:\Users\Oren\Source\Main\iOS.Client\bin\iPhoneSimulator\Debug\iOS_Client.exe not found. Can be ignored if not a NUnit project.
Dependent Assembly monotouch, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065 of C:\Users\Oren\Source\Main\iOS.Common\bin\iPhone\Debug\iOS.Common.dll not found. Can be ignored if not a NUnit project.
NUnit 1.0.0.0 discovering test is finished
========== Discover test finished: 0 found (0:00:02.3111359) ==========

Tested with Test Adapter Release 1.0
Since VS2012 Update 2, you can also group unit tests via Class name. However, when using inheritance, sub classes are grouped via their parent name.
Example:
class Parent
Sub DoSth()
End Class
Class Child
inherits Parent
End Class
DoSth() will turn up two times in the test explorer - in two categories, both called "Parent".
This might or might not be related: TestContext.CurrentContext.Test.FullName returns
"Namespace.Parent.DoSth" for the parent class method, and "Namespace.Child.Parent.DoSth" for the child class. I guess the class hierarchy should be inverted.

Hi,

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 1.2.0.0 discovering tests is started
NUnit 1.2.0.0 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 1.2.0.0

Cheers,

James

I found a stackoverflow question that discusses this very issue.
That question has to do with the ReSharper test runner, but the same buggy behavior exists in the NUnit VS adapter.

The NUnit standalone runner works correctly, so this bug is probably not in NUnit Core.

I'm a bit surprised that this has not been reported before, or fixed yet, as abstract test fixtures are getting increasingly popular.

Any workarounds (or even better, a quick fix) are greatly appreciated, this technique is a core part of our current test plan.

EDIT: It turns out that running tests explicitly from the test class node in Test Explorer does run all the tests and test cases in the base class.

However:

1. Running tests using CtrlR+CtrlT (TestExplorer.DebugAllTestsInContext) runs only the [Test]'s in the base class, not the [TestCase]'s.

2. Double clicking on a such a TestCase in Test Explorer does not navigate to the correct file and line in the abstract text fixture.

This reduces the severity to a major inconvenience, but at least there is a workaround. A fix is still very appreciated.

When Debugging a failing synchronous unit test, Visual Studio will break into the debugger as the Exception is thrown (with break on exceptions set to User-Unhandled). However, with an async nunit test, it looks like the exception is being swallowed by the test runner and does not cause VS to break. Setting break on exceptions to "Thrown" WILL cause it to break.

Sample Code:

[TestFixture]
public class SampleFixture
{
    [Test]
    public async Task AsyncTest()
    {
        Assert.Fail();
    }

    [Test]
    public void SyncTest()
    {
        Assert.Fail();
    }
}

Instructions to reproduce:

• Start a new Class Library project in Visual Studio (tested under 2012 and 2013 Preview, tested with Framework 4.5 project).
• Add the above code as a class
• Build the project
• Ensure "Break on Exceptions" is set to "User-Unhandled" for "Common Language Runtime Exceptions"
• Right click "SyncTest" in Test Explorer, click "Debug Selected Tests". Visual studio will automatically break at the Assert.Fail line.
• Right click "AsyncTest" in Test Explorer, click "Debug Selected Tests". Visual Studio will go into debug mode, and finish immediately without breaking into the debugger. Test failure will still be recorded in the Test Explorer.

See discussion at https://bugs.launchpad.net/nunit-vs-adapter/+bug/1210535

In case, when TestFixture inherits from (generic) class, which contains tests,

1. the tests in inherited class and the base class are displayed separately
2. "Browse th source" for tests in base class is not available

example:

class EntityEditTests<TEntity>
{
    [Test]
    public void DeleteEntity()
   {
           ...
   }
}

[TestFixture]
class DocumentTests : EntityEditTests<Document>
{
    [Test]
    public void SignDocument
   {
           ...
   }
}

^{[jnm2—edited to add code fences so that generics weren't interpreted as HTML elements]}

Instead of showing two tests for DocumentTests, one test for DocumentTests is displayed and one test for EntityEditTests' !

See discussion at https://bugs.launchpad.net/nunit-vs-adapter/+bug/1194734

I have a base class containing methods with TestFixtureSetUpAttribute/TestFixtureTearDown attributes and a child class that contains three tests. If I group the tests by class in Test Explorer and right-click on the class name and select Run, those methods correctly get called only once. If however I click "Run All" at the top, they each get called three times, once per test

[EDIT] Never mind, this was a problem with my VS configuration. I fixed it by going to the Test menu -> Test Settings -> Default Processor Architecture -> x64. Sorry for the trouble, please close this ticket.

I'm using the Test Adapter from the VS Extensions menu, v1.0.0.0.

One of my projects must be compiled as x64, and the Test Adapter doesn't find any of the tests in that project. Switching it to Any CPU or x86 will show the tests in the Test Explorer.

The tests do appear and run properly in the NUnit GUI when they are built as x64, just the Test Explorer is not showing them.

You should be able to repro this by making a new project in VS, writing some tests, changing the platform target to x64, and building. If you add a second project with some more unit tests and start mixing the build modes, you should see the tests always disappear from the Test Explorer in the x64 projects.

Tried it on VS 2012 Ultimate and VS 2013 Premium, both have the same issue.

I'm using NUnit with AutoFixture, AutoMoq and the Theory attribute.

Here is my test method,

[TestFixture]
public class TestClass
{
    [Theory, AutoMoqData]
    public void TestI(I i)
    { }

}

the interface

public interface I
{ }

and the attribute

public class AutoMoqDataAttribute : AutoDataAttribute
{
    public AutoMoqDataAttribute()
        : base(new Fixture().Customize(new AutoMoqCustomization()))
    { }
}

When I build my solution the test is discovered. When I run the test the following is written to the Output window:

NUnit 1.0.0.0 executing tests is started
Run started: [...].Test.dll
NUnit 1.0.0.0 executing tests is finished
Test adapter sent back a result for an unknown test case. Ignoring result for 'TestI(Mock<TestClass+I:1393>.Object)'.

Why is not it working with NUnit? (It works fine with both xUnit.net and TestDriven.Net.)

I have the following Nuget packages installed in the test project:

• AutoFixture 3.18.1
• AutoFixture.AutoMoq 3.18.1
• Moq 4.2.1402.2112
• NUnit 2.6.3
• NUnitTestAdapter 1.0

I'm running the test from within Visual Studio 2013 Professional. I also tried running the test in the separate GUI runner, with the same result.

This is basically the last example from here, except it's not working.
http://madstt.dk/nunit-support-for-autofixture

I'm using the following code (more or less, obviously):

[Test]
public void TestMethod1()
{
    Assert.That(1+2, Is.EqualTo(3));
}

[TestCase(1, 2, 3 )]
[TestCase(4, 5, 9 )]
public void TestMethod2(int first, int second, int sum)
{
    Assert.That(first + second, Is.EqualTo(sum));
}

In the Test Explorer, three tests are discovered (which is what I'd expect). However, the Code Lens feature in VS 2013 only shows the non-parameterised method as a test.

In addition to Code Lens not identifying test source code, methods under test which are tested by a parameterised test method do not detect any tests for themselves (or show only other tests that are not parameterised), which means that tests already written when implementing a method cannot be run directly from that method's source.

I'm using VS 2013 Ultimate Update 1, targetting .net 4.5.1 and using NUnit 2.6.3 with Test Adapter 1.0.0.0.

Notes:

1. The same thing happens with tests parameterised using the TestCaseSource attribute.
2. If some tests (non-parameterised tests) show up for a testable method in Code Lens, selecting "Run All" from here actually runs all the tests, but only results ("x/y passing" & the test list popup) from the detected tests show up in Code Lens.
3. Changing the name of TestMethod2 to TestMethod1 (i.e. the same as the first one) results in it being identified as a test by Code Lens, but nothing else changes

In documentation of 2.6.3 version, i read "All updates including Update 2 CTP2 checked March 2014".
When a version supporting vs2013 update 3 will be available?
Regards,

I have been helping someone install NUnit Adapter in their VS2012 installation when I noticed that when we attempt to run a test which will run under version 1.0.0.0 of NUnit, this message comes up:

I checked versions on my system and I WAS running 1.0.0.0 which works and runs all tests perfectly fine. I saw there was an update available and so to isolate the issue I updated my version to 1.1.0.0. However, my system is now broken in the same manner as my colleagues'.

I assumed this had something to do with the version of NUnit framework we were using. I went to the NUnit website and downloaded the 2.6.3. msi file and attempted to install it when I was met with this error message:

I saw that it was looking for a specific .NET version (2.0 or 4.0), so I then downloaded the .NET 4.0 web install package and started it when I discovered .NET 4.0 was already installed:

This was very frustrating to say the least. I read quite a bit of bug history on this issue and it seems it is a common one amongst many people. The fact that I can repeat this on two different systems using NUnit Adapter as an extension in VS2012 Update 4 lends credence to this being a real bug and not just a nuisance on some systems.

I want to roll back my NUnit Adapter extension to version 1.0.0.0. Can you provide me with an installer for this version?

.

As of today, I started getting the following error.

------ Discover test started ------
Failed to configure settings for runsettings plugin 'VSTest Run Configuration' as it threw following exception:
'Method not found: 'System.String Microsoft.VisualStudio.TestPlatform.ObjectModel.ValidateArg.NotNullOrEmpty(System.String, System.String)'.'
Please contact the plugin author.

I don't know if this is related to the most recent release in NuGet or not.

We are trying to write an NUnit plugin for FsCheck (github.com/fsharp/fscheck). The addin works fine with the standalone test runner, although it is not shown in the addin dialog. According to this converstaion in the mailing list, this is because the addin is built with .NET 4.0:

https://groups.google.com/forum/#!topic/nunit-discuss/je0VXIsVQNQ

The addin is also written and compiled using F# (3.0).

The addin does not work with the test adapter - we've tried putting the addin and its dependencies in the addins folder where the adapter lives, as well in the folder itself. It looks like it is never loaded.

It's not clear how to go about writing an addin for NUnit that works with the standalone runner, the test adapter, the test adapter NuGet package, and Resharper.

From https://bugs.launchpad.net/nunit-vs-adapter/+bug/1193957

Software verions: Visual Studio 2013, Windows 7 Ultimate, Nunit Test Adapter ver 1.2.0.0

Steps to reproduce:

• Start Visual Studio and open a solution with a unit test project written for NUnit.
• Find a unit test and right click on it selecting "run selected unit tests" from the context menu.
• Unit test is executed.

Expected Results:

• Nothing extra is added to the project definition.

Actual Results:

• The following has been added to all nunit projects,

 <ItemGroup>
    <Service Include="{82A7F48D-3B50-4B1E-B82E-3ADA8210C358}" />
  </ItemGroup>

I need to play nice with others. My use of this tool shouldn't pollute my project files.

hi,
i'm tryint to integrate NUnit in my Project. i set in TestSettings1.testsettings and False and in .testsettings root folder for the assmlies to be loaded %HOMEDRIVE%\myproject\bin
but the settings are ignored

We have a project that has some dll's from the Unity Game engine that cause this exception during the test discovery. We don't really care about trying to test anything from that dll, but the problem is it is blocking test discovery for our Nunit based unit tests that have no references to anything in the problematic dll.

Could we catch this exception, I believe in the NUnitTestDiscoverer, which already seems to handle other types of exceptions? Please let me know if there is any information I can provide that can help this along.

As an addendum, we did try to pull down the code and build/add the try/catch ourselves, however we failed spectacularly at simply trying to build the project with VS 2010, 2012, and 2013. We had to comment out a number of lines of code to get it to build and broke much in the process.

The adapter uses NUnit 2.6.3, which cannot reliably run tests written for NUnit 3.0. It should examine the version of the referenced framework assembly and not try to discover tests if the version is 3.0 or more.

With NUNit Test Adapter 1.0.0.0:

vstest.console.exe NUnitTestAssembly.dll /UseVsixExtensions:true
->
Test Run Successful

With NUNit Test Adapter 1.1.0.0:

vstest.console.exe NUnitTestAssembly.dll /UseVsixExtensions:true
->
Warning: No test available
Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

We've got tests that load DLLs dynamically, and the shadow copy mechanism within NUnit fails to copy these DLLs to the temporary directory where the test are run from.

The simple work around we've been using in NUnit (as well as Reshaprer's NUinit runner) is to disable shadow copy in the options.

The NUnit Test Adapter for Visual Studio doesn't allow us to disable Shadow Copy and therefore prevents our use of NUnit within Visual Studio 2012.

Could you add the ability to disable Shadow Copy to the adapter?

See discussion at https://bugs.launchpad.net/nunit-vs-adapter/+bug/1084284

Hi,

I got a strange error when I want to run NUnit Tests in TFS 2013 Update 2. We used the latest Version of NUnit (NUnit 1.1.0.2).

I, 2228, 1, 2014/07/01, 10:37:11.392, 2752084083050, vstest.executionengine.x86.exe, TestExecutorService: Starting TestExecutor with command-line arguments /parentProcessId;1784
I, 2228, 1, 2014/07/01, 10:37:11.517, 2752085320643, vstest.executionengine.x86.exe, TestExecutorService: Created/Started the listening channel. ChannelUri=net.pipe://computername/TestExecutor/2228
V, 2228, 5, 2014/07/01, 10:37:12.720, 2752097302700, vstest.executionengine.x86.exe, TestExecutorWebService:ValidateUser: Validating user 'USERBGVM***'.
V, 2228, 5, 2014/07/01, 10:37:12.720, 2752097333575, vstest.executionengine.x86.exe, TestExecutorWebService: Received InitializeConnection.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097390963, vstest.executionengine.x86.exe, TestPluginCache: Updating loadOnlyWellKnownExtensions from False to False.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097438406, vstest.executionengine.x86.exe, TestPluginCache: Ignoring extension D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\src\Vita.TestNunit.Tests\Microsoft.VisualStudio.TestPlatform.ObjectModel.dll as it does not exist.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097439292, vstest.executionengine.x86.exe, TestPluginCache: Ignoring extension D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\src\Vita.TestNunit.Tests\msdia110typelib_clr0200.dll as it does not exist.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097440430, vstest.executionengine.x86.exe, TestPluginCache: Ignoring extension D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\src\Vita.TestNunit.Tests\nunit.core.dll as it does not exist.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097441151, vstest.executionengine.x86.exe, TestPluginCache: Ignoring extension D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\src\Vita.TestNunit.Tests\nunit.core.interfaces.dll as it does not exist.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097441736, vstest.executionengine.x86.exe, TestPluginCache: Ignoring extension D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\src\Vita.TestNunit.Tests\nunit.util.dll as it does not exist.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097442425, vstest.executionengine.x86.exe, TestPluginCache: Ignoring extension D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\src\Vita.TestNunit.Tests\NUnit.VisualStudio.TestAdapter.dll as it does not exist.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097453286, vstest.executionengine.x86.exe, TestPluginCache: Using directories for assembly resolution 'C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies'.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097464550, vstest.executionengine.x86.exe, TestPluginCache: Updated the available extensions to 'C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\Microsoft.VisualStudio.TestPlatform.ObjectModel.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\msdia110typelib_clr0200.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\nunit.core.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\nunit.core.interfaces.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\nunit.util.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\NUnit.VisualStudio.TestAdapter.dll'.
V, 2228, 5, 2014/07/01, 10:37:12.736, 2752097470032, vstest.executionengine.x86.exe, TestExecutorWebService: Handled InitializeConnection.
V, 2228, 6, 2014/07/01, 10:37:12.736, 2752097511446, vstest.executionengine.x86.exe, TestExecutorService: Loading the extensions
V, 2228, 6, 2014/07/01, 10:37:12.799, 2752098117128, vstest.executionengine.x86.exe, TestPluginCache: Creating the plugin discoverer.
V, 2228, 6, 2014/07/01, 10:37:12.799, 2752098127594, vstest.executionengine.x86.exe, TestPluginCache: Discovering the extensions using extension path.
V, 2228, 5, 2014/07/01, 10:37:12.986, 2752099957883, vstest.executionengine.x86.exe, TestExecutorWebService:ValidateUser: Validating user 'USERBGVM***'.
V, 2228, 5, 2014/07/01, 10:37:12.986, 2752099958900, vstest.executionengine.x86.exe, TestExecutorWebService: Received StartTestRun.
V, 2228, 5, 2014/07/01, 10:37:12.986, 2752099993317, vstest.executionengine.x86.exe, TestExecutorService: StartTestRun: Validating the parameters.
V, 2228, 5, 2014/07/01, 10:37:12.986, 2752100005664, vstest.executionengine.x86.exe, TestExecutorService: StartTestRun: Validated the parameters.
I, 2228, 6, 2014/07/01, 10:37:13.455, 2752104651137, vstest.executionengine.x86.exe, AssemblyResolver: nunit.core: Resolving assembly.
I, 2228, 6, 2014/07/01, 10:37:13.470, 2752104772021, vstest.executionengine.x86.exe, AssemblyResolver: nunit.core: Resolved assembly.
I, 2228, 6, 2014/07/01, 10:37:13.502, 2752105219412, vstest.executionengine.x86.exe, AssemblyResolver: nunit.core.interfaces: Resolving assembly.
I, 2228, 6, 2014/07/01, 10:37:13.517, 2752105235049, vstest.executionengine.x86.exe, AssemblyResolver: nunit.core.interfaces: Resolved assembly.
I, 2228, 6, 2014/07/01, 10:37:13.517, 2752105267568, vstest.executionengine.x86.exe, AssemblyResolver: nunit.util: Resolving assembly.
I, 2228, 6, 2014/07/01, 10:37:13.533, 2752105495071, vstest.executionengine.x86.exe, AssemblyResolver: nunit.util: Resolved assembly.
I, 2228, 6, 2014/07/01, 10:37:13.549, 2752105559249, vstest.executionengine.x86.exe, AssemblyResolver: NUnit.VisualStudio.TestAdapter: Resolving assembly.
I, 2228, 6, 2014/07/01, 10:37:13.642, 2752106513596, vstest.executionengine.x86.exe, AssemblyResolver: NUnit.VisualStudio.TestAdapter: Resolved assembly.
V, 2228, 6, 2014/07/01, 10:37:13.642, 2752106527708, vstest.executionengine.x86.exe, TestPluginCache: Discovered the extensions using extension path 'C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\Microsoft.VisualStudio.TestPlatform.ObjectModel.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\msdia110typelib_clr0200.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\nunit.core.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\nunit.core.interfaces.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\nunit.util.dll,C:\Users\tadvxth\AppData\Local\Temp\BuildAgent\15\Assemblies\NUnit.VisualStudio.TestAdapter.dll'.
V, 2228, 6, 2014/07/01, 10:37:13.642, 2752106541530, vstest.executionengine.x86.exe, TestPluginCache: Discoverers are 'Microsoft.VisualStudio.TestPlatform.Extensions.GenericTestAdapter.GenericTestDiscoverer, Microsoft.VisualStudio.TestPlatform.Extensions.GenericTestAdapter, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter.MSAppContainerTestDiscoverer, Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,Microsoft.VisualStudio.TestPlatform.Extensions.OrderedTestAdapter.OrderedTestDiscoverer, Microsoft.VisualStudio.TestPlatform.Extensions.OrderedTestAdapter, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestDiscoverer, Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,Microsoft.VisualStudio.TestTools.CppUnitTestFramework.CppUnitTestExtension.TestDiscoverer, Microsoft.VisualStudio.TestTools.CppUnitTestFramework.CppUnitTestExtension, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,NUnit.VisualStudio.TestAdapter.NUnitTestDiscoverer, NUnit.VisualStudio.TestAdapter, Version=1.1.0.2, Culture=neutral, PublicKeyToken=4cb40d35494691ac'.
V, 2228, 6, 2014/07/01, 10:37:13.642, 2752106542095, vstest.executionengine.x86.exe, TestPluginCache: Executors are 'executor://GenericTestAdapter/v1,executor://MSAppContainerTestAdapter/v1,executor://OrderedTestAdapter/v1,executor://MSTestAdapter/v1,executor://CppUnitTestExecutor/v1,executor://NUnitTestExecutor'.
V, 2228, 6, 2014/07/01, 10:37:13.642, 2752106542428, vstest.executionengine.x86.exe, TestPluginCache: Setting providers are 'DataCollectionRunSettings,RunConfiguration,MSAppContainerTest,MSTest'.
V, 2228, 6, 2014/07/01, 10:37:13.642, 2752106542765, vstest.executionengine.x86.exe, TestPluginCache: Loggers are 'logger://Microsoft/TestPlatform/ConsoleLogger/v1,logger://Microsoft/TestPlatform/TfsLogger/v1,logger://Microsoft/TestPlatform/TrxLogger/v1'.
I, 2228, 5, 2014/07/01, 10:37:13.658, 2752106642688, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.RunConfigurationSettingsProvider
V, 2228, 5, 2014/07/01, 10:37:13.658, 2752106699090, vstest.executionengine.x86.exe, TestExecutorService: PopulateTestRunContext: Executor process is expected to shutdown after the test run.
V, 2228, 5, 2014/07/01, 10:37:13.658, 2752106699687, vstest.executionengine.x86.exe, TestExecutorService: StartTestRun: Created the test run context IsDataCollectionEnabled=False, AreTestCaseLevelEventsRequired=False.
I, 2228, 6, 2014/07/01, 10:37:13.658, 2752106727623, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.GenericTestAdapter.GenericTestDiscoverer
V, 2228, 6, 2014/07/01, 10:37:13.658, 2752106729133, vstest.executionengine.x86.exe, TestDiscoveryManager: LoadExtensions: Created discoverer Microsoft.VisualStudio.TestPlatform.Extensions.GenericTestAdapter.GenericTestDiscoverer
I, 2228, 6, 2014/07/01, 10:37:13.658, 2752106730225, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter.MSAppContainerTestDiscoverer
V, 2228, 6, 2014/07/01, 10:37:13.658, 2752106731197, vstest.executionengine.x86.exe, TestDiscoveryManager: LoadExtensions: Created discoverer Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter.MSAppContainerTestDiscoverer
I, 2228, 6, 2014/07/01, 10:37:13.658, 2752106732494, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.OrderedTestAdapter.OrderedTestDiscoverer
V, 2228, 6, 2014/07/01, 10:37:13.658, 2752106733679, vstest.executionengine.x86.exe, TestDiscoveryManager: LoadExtensions: Created discoverer Microsoft.VisualStudio.TestPlatform.Extensions.OrderedTestAdapter.OrderedTestDiscoverer
I, 2228, 6, 2014/07/01, 10:37:13.658, 2752106734843, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestDiscoverer
V, 2228, 6, 2014/07/01, 10:37:13.658, 2752106737171, vstest.executionengine.x86.exe, TestDiscoveryManager: LoadExtensions: Created discoverer Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestDiscoverer
I, 2228, 6, 2014/07/01, 10:37:13.658, 2752106738485, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestTools.CppUnitTestFramework.CppUnitTestExtension.TestDiscoverer
V, 2228, 6, 2014/07/01, 10:37:13.658, 2752106739446, vstest.executionengine.x86.exe, TestDiscoveryManager: LoadExtensions: Created discoverer Microsoft.VisualStudio.TestTools.CppUnitTestFramework.CppUnitTestExtension.TestDiscoverer
I, 2228, 6, 2014/07/01, 10:37:13.674, 2752106761759, vstest.executionengine.x86.exe, AssemblyResolver: NUnit.VisualStudio.TestAdapter, Version=1.1.0.2, Culture=neutral, PublicKeyToken=4cb40d35494691ac: Resolving assembly.
I, 2228, 6, 2014/07/01, 10:37:13.674, 2752106767416, vstest.executionengine.x86.exe, AssemblyResolver: NUnit.VisualStudio.TestAdapter, Version=1.1.0.2, Culture=neutral, PublicKeyToken=4cb40d35494691ac: Resolved assembly.
I, 2228, 6, 2014/07/01, 10:37:13.674, 2752106768264, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: NUnit.VisualStudio.TestAdapter.NUnitTestDiscoverer
V, 2228, 6, 2014/07/01, 10:37:13.674, 2752106810683, vstest.executionengine.x86.exe, TestDiscoveryManager: LoadExtensions: Created discoverer NUnit.VisualStudio.TestAdapter.NUnitTestDiscoverer
V, 2228, 6, 2014/07/01, 10:37:13.674, 2752106811164, vstest.executionengine.x86.exe, TestExecutorService: Loaded the discoverers
I, 2228, 6, 2014/07/01, 10:37:13.674, 2752106872935, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.GenericTestAdapter.GenericTestExecutor
V, 2228, 6, 2014/07/01, 10:37:13.674, 2752106874111, vstest.executionengine.x86.exe, TestExecutorExtensionManager: Loading executor Microsoft.VisualStudio.TestPlatform.Extensions.GenericTestAdapter.GenericTestExecutor
I, 2228, 6, 2014/07/01, 10:37:13.674, 2752106875223, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter.MSAppContainerTestExecutor
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106939630, vstest.executionengine.x86.exe, TestExecutorExtensionManager: Loading executor Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter.MSAppContainerTestExecutor
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106941343, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.OrderedTestAdapter.OrderedTestExecutor
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106943303, vstest.executionengine.x86.exe, TestExecutorExtensionManager: Loading executor Microsoft.VisualStudio.TestPlatform.Extensions.OrderedTestAdapter.OrderedTestExecutor
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106944508, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestExecutor
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106957613, vstest.executionengine.x86.exe, TestExecutorExtensionManager: Loading executor Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestExecutor
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106958726, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestTools.CppUnitTestFramework.CppUnitTestExtension.TestExecutor
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106964352, vstest.executionengine.x86.exe, TestExecutorExtensionManager: Loading executor Microsoft.VisualStudio.TestTools.CppUnitTestFramework.CppUnitTestExtension.TestExecutor
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106965343, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: NUnit.VisualStudio.TestAdapter.NUnitTestExecutor
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106967378, vstest.executionengine.x86.exe, TestExecutorExtensionManager: Loading executor NUnit.VisualStudio.TestAdapter.NUnitTestExecutor
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106967662, vstest.executionengine.x86.exe, TestExecutorService: Loaded the executors
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106978096, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.DataCollectorsSettingsProvider
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106979328, vstest.executionengine.x86.exe, SettingsProviderExtensionManager: Loading settings provider Microsoft.VisualStudio.TestPlatform.Extensions.DataCollectorsSettingsProvider
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106979610, vstest.executionengine.x86.exe, SettingsProviderExtensionManager: Loading settings provider Microsoft.VisualStudio.TestPlatform.Extensions.RunConfigurationSettingsProvider
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106980514, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter.MSAppContainerAdapterSettingsProvider
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106981470, vstest.executionengine.x86.exe, SettingsProviderExtensionManager: Loading settings provider Microsoft.VisualStudio.TestPlatform.Extensions.MSAppContainerAdapter.MSAppContainerAdapterSettingsProvider
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106982535, vstest.executionengine.x86.exe, TestPluginManager.CreateTestExtension: Attempting to load test extension: Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestSettingsProvider
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106983297, vstest.executionengine.x86.exe, SettingsProviderExtensionManager: Loading settings provider Microsoft.VisualStudio.TestPlatform.Extensions.VSTestIntegration.MSTestSettingsProvider
V, 2228, 6, 2014/07/01, 10:37:13.689, 2752106983515, vstest.executionengine.x86.exe, TestExecutorService: Loaded the settings providers
I, 2228, 6, 2014/07/01, 10:37:13.689, 2752106983721, vstest.executionengine.x86.exe, TestExecutorService: Loaded the extensions
V, 2228, 5, 2014/07/01, 10:37:13.705, 2752107223933, vstest.executionengine.x86.exe, TestExecutorService: StartTestRun: Started the test run.
V, 2228, 5, 2014/07/01, 10:37:13.705, 2752107224476, vstest.executionengine.x86.exe, TestExecutorWebService: Handled StartTestRun.
I, 2228, 7, 2014/07/01, 10:37:13.752, 2752107609337, vstest.executionengine.x86.exe, AssemblyResolver: Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a: Resolving assembly.
I, 2228, 7, 2014/07/01, 10:37:13.752, 2752107612214, vstest.executionengine.x86.exe, AssemblyResolver: Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a: Resolving assembly.
V, 2228, 7, 2014/07/01, 10:37:13.752, 2752107621233, vstest.executionengine.x86.exe, TestExtensionResolver:Resolving assembly 'Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
V, 2228, 7, 2014/07/01, 10:37:13.752, 2752107624620, vstest.executionengine.x86.exe, TestExtensionResolver: Failed to load the assembly 'Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
I, 2228, 7, 2014/07/01, 10:37:13.752, 2752107625823, vstest.executionengine.x86.exe, AssemblyResolver: Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a: Resolving assembly.
I, 2228, 7, 2014/07/01, 10:37:13.752, 2752107626948, vstest.executionengine.x86.exe, AssemblyResolver: Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a: Resolving assembly.
V, 2228, 7, 2014/07/01, 10:37:13.752, 2752107629266, vstest.executionengine.x86.exe, TestExtensionResolver:Resolving assembly 'Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
V, 2228, 7, 2014/07/01, 10:37:13.752, 2752107631785, vstest.executionengine.x86.exe, TestExtensionResolver: Failed to load the assembly 'Microsoft.VisualStudio.TestPlatform.Utilities.PhoneAppContainer, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
I, 2228, 7, 2014/07/01, 10:37:13.752, 2752107633264, vstest.executionengine.x86.exe, TestDiscoveryManager: Discovering tests from sources D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\bin\Vita.TestNunit.Tests.dll
V, 2228, 7, 2014/07/01, 10:37:13.752, 2752107695106, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Running tests for executor://MSAppContainerTestAdapter/v1
V, 2228, 7, 2014/07/01, 10:37:13.814, 2752108214988, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Completed running tests for executor://MSAppContainerTestAdapter/v1
V, 2228, 7, 2014/07/01, 10:37:13.814, 2752108215605, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Running tests for executor://MSTestAdapter/v1
V, 2228, 7, 2014/07/01, 10:37:13.814, 2752108263493, vstest.executionengine.x86.exe, MixedModeExecutor: Started doing deployment for source D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\bin\Vita.TestNunit.Tests.dll.
V, 2228, 7, 2014/07/01, 10:37:13.830, 2752108445483, vstest.executionengine.x86.exe, Removing source D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\bin\Vita.TestNunit.Tests.dll from the source list as it does not contain any test.
V, 2228, 7, 2014/07/01, 10:37:13.830, 2752108446338, vstest.executionengine.x86.exe, MixedModeExecutor: Deployment done for all the sources D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\bin\Vita.TestNunit.Tests.dll.
V, 2228, 7, 2014/07/01, 10:37:13.830, 2752108448771, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Completed running tests for executor://MSTestAdapter/v1
V, 2228, 7, 2014/07/01, 10:37:13.830, 2752108449160, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Running tests for executor://CppUnitTestExecutor/v1
V, 2228, 7, 2014/07/01, 10:37:13.877, 2752108964721, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Completed running tests for executor://CppUnitTestExecutor/v1
V, 2228, 7, 2014/07/01, 10:37:13.877, 2752108965277, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Running tests for executor://NUnitTestExecutor
V, 2228, 7, 2014/07/01, 10:37:13.892, 2752109003095, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notifying the callback about the test run message 'NUnit 1.1.0.2 executing tests is started'
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111483276, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notified the callback about the test run message 'NUnit 1.1.0.2 executing tests is started'.
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111537923, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notifying the callback about the test run message 'Exception System.InvalidOperationException, Exception thrown executing tests'
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111556965, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notified the callback about the test run message 'Exception System.InvalidOperationException, Exception thrown executing tests'.
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111557618, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notifying the callback about the test run message 'NUnit 1.1.0.2 executing tests is finished'
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111567744, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notified the callback about the test run message 'NUnit 1.1.0.2 executing tests is finished'.
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111568138, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Completed running tests for executor://NUnitTestExecutor
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111579131, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notifying the callback about the test run message 'No test is available in D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\bin\Vita.TestNunit.Tests.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.'
V, 2228, 7, 2014/07/01, 10:37:14.142, 2752111592705, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunMessage: Notified the callback about the test run message 'No test is available in D:\Arbeitsbereiche\APPLICATIONS\Test_UnitTests\bin\Vita.TestNunit.Tests.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.'.
V, 2228, 7, 2014/07/01, 10:37:14.158, 2752111710724, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunComplete: Cleaning up the run context and notifying the callback about testRun completion, IsCanceled=False, Total tests=0.
V, 2228, 7, 2014/07/01, 10:37:14.158, 2752111711406, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunComplete: Cleaning up the test run context.
V, 2228, 7, 2014/07/01, 10:37:14.158, 2752111711813, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunComplete: Cleaned up the test run context.
V, 2228, 7, 2014/07/01, 10:37:14.205, 2752112137949, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunComplete: Notified the callback about testRun completion, IsCanceled=False.
V, 2228, 7, 2014/07/01, 10:37:14.205, 2752112138473, vstest.executionengine.x86.exe, TestExecutorService: OnTestRunComplete: Executor process is shutting down after the test run.
V, 2228, 7, 2014/07/01, 10:37:14.205, 2752112138801, vstest.executionengine.x86.exe, TestExecutionManager.RunTests: Run is complete.
V, 2228, 1, 2014/07/01, 10:37:14.205, 2752112194386, vstest.executionengine.x86.exe, TestExecutorService: CancelTestRun: Validating the call.
I, 2228, 1, 2014/07/01, 10:37:14.220, 2752112284865, vstest.executionengine.x86.exe, TestExecutorMain.InternalStop: Exception received while canceling test run. System.InvalidOperationException: The cancelation of the test run is not possible as there is no test run which is in progress.
at Microsoft.VisualStudio.TestPlatform.TestExecutor.TestExecutorService.CancelTestRun()
at Microsoft.VisualStudio.TestPlatform.TestExecutor.TestExecutorMain.InternalStop().
V, 2228, 1, 2014/07/01, 10:37:14.267, 2752112741906, vstest.executionengine.x86.exe, TestExecutorService: CancelTestRun: Validating the call.
I, 2228, 1, 2014/07/01, 10:37:14.267, 2752112745077, vstest.executionengine.x86.exe, TestExecutorMain.InternalStop: Exception received while canceling test run. System.InvalidOperationException: The cancelation of the test run is not possible as there is no test run which is in progress.
at Microsoft.VisualStudio.TestPlatform.TestExecutor.TestExecutorService.CancelTestRun()
at Microsoft.VisualStudio.TestPlatform.TestExecutor.TestExecutorMain.InternalStop().