<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NUnit on Hermit Blog</title><link>https://hermit.no/categories/nunit/</link><description>Recent content in NUnit on Hermit Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 29 Dec 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://hermit.no/categories/nunit/index.xml" rel="self" type="application/rss+xml"/><item><title>How to extend the NUnit constraints</title><link>https://hermit.no/nunit/how-to-extend-the-nunit-constraints/</link><pubDate>Sun, 29 Dec 2024 00:00:00 +0000</pubDate><guid>https://hermit.no/nunit/how-to-extend-the-nunit-constraints/</guid><description>&lt;p&gt;&lt;a href="http://nunit.org/"&gt;NUnit&lt;/a&gt; has a very rich and readable constraint set. Normally you don’t need to do anything. But, there are some cases where it would be nice to be able to tweak these constraints. You can always wrap them and extend them that way, but then you lose all the other good stuff, like chaining. What is not so well known is that you can extend the existing constraints, they are **designed** to be extendable! In this post I will show how you can do that easily.&lt;/p&gt;</description></item><item><title/><link>https://hermit.no/nunit/debugging-the-nunit3testadapter-take2/</link><pubDate>Sun, 20 Sep 2020 00:00:00 +0000</pubDate><guid>https://hermit.no/nunit/debugging-the-nunit3testadapter-take2/</guid><description>&lt;h1 id="debugging-the-nunit3testadapter-take-2"&gt;Debugging the NUnit3TestAdapter Take 2&lt;/h1&gt;&#10;&lt;h2 id="background"&gt;Background&lt;/h2&gt;&#10;&lt;p&gt;In version 4.2 of the NUnit3TestAdapter debugging has been made a bit simpler. For the earlier versions, see &lt;a href="http://hermit.no/debugging-the-nunit3testadapter/"&gt;Debugging the NUnit3TestAdapter&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;A test adapter sits between a TestHost and the test framework. If you use Visual Studio or dotnet, both starts up a TestHost as a separate process. The testhost is responsible for locating the adapters, and then invoke them to run the test frameworks on the test code. Debugging an adapter is hard, because it sits between these two processes, of which you have no control. The way to handle this is to enable launching the adapter in debug mode. This post details how you do that.&lt;/p&gt;</description></item><item><title/><link>https://hermit.no/nunit/debugging-the-nunit3testadapter/</link><pubDate>Tue, 19 Nov 2019 00:00:00 +0000</pubDate><guid>https://hermit.no/nunit/debugging-the-nunit3testadapter/</guid><description>&lt;h1 id="debugging-the-nunit3testadapter"&gt;Debugging the NUnit3TestAdapter&lt;/h1&gt;&#10;&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;A test adapter sits between a TestHost and the test framework. If you use Visual Studio or dotnet, both starts up a TestHost as a seperate process. The testhost is responsible for locating the adapters, and then invoke them to run the test frameworks on the test code. Debugging the adapters is hard, because it sits between these processes, of which you have no control. The way to handle this is to enable launching the debugger from inside the adapter code. This post details how you do that.&lt;/p&gt;</description></item><item><title>A story on working with NUnit backward compatibility, and dependencies</title><link>https://hermit.no/archive/2019-01-26-a-story-on-working-with-nunit-backward-compatibility-and-dependencies/</link><pubDate>Sat, 26 Jan 2019 20:18:27 +0100</pubDate><guid>https://hermit.no/archive/2019-01-26-a-story-on-working-with-nunit-backward-compatibility-and-dependencies/</guid><description>&lt;p&gt;NUnit as a project has a tradition of keeping backwards compatibility. It ensures that even if you stay on a earlier version of Visual Studio, .net FrameWork, or whatever it is, NUnit should continue to work even with upgrades of NUnit.&#10;So also for the NUnitAdapter. It should work on any version of Visual Studio after the 2012 version. We have managed to maintain that.&#10;However, over time it has become harder and harder to verify the compatibility. Microsoft has increased their release pace, and the number of versions and variations of Visual Studio has subsequently increased tremendously over the last years. We have not found an easy way to test all the possible variations, so have had to do a set of minimum tests, then respond quickly when someone raises an issue. Fortunately, there have not been many of those. We rely to a large degree on peer reviews using pull requests, which have weeded out most of these issues.&lt;/p&gt;</description></item><item><title>How to convert NUnit Assert.AreEqual to fluent Assert.That syntax easily</title><link>https://hermit.no/nunit/how-to-convert-nunit-assert.areequal-to-fluent-assert.that-syntax-easily/</link><pubDate>Sat, 03 Nov 2018 22:44:25 +0100</pubDate><guid>https://hermit.no/nunit/how-to-convert-nunit-assert.areequal-to-fluent-assert.that-syntax-easily/</guid><description>&lt;p&gt;Once upon a time it was declared that an Assert statement should have constraints given as AreEqual and AreNotEqual.&#10;Further it was declared that it should be written in the opposite way of how a developer will think, that is with the expected value first and the actual value last.&#10;Why this was made so, is still unknown.&lt;/p&gt;&#10;&lt;p&gt;But we end up with tons of code like:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-csharp" data-lang="csharp"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;Assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;AreEqual&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;Zulu&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;zulu&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;Assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;AreEqual&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;Z - Zulu&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;zulu&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Description&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;Assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;AreEqual&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;FlagType&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Signal&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;zulu&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Sort&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;Assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;AreEqual&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="m"&gt;0.7&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;zulu&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;AspectRatio&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;And it is not uncommon to see the two parameters swapped, making the displayed results harder to interpret.&lt;/p&gt;&#10;&lt;p&gt;If we write this with the fluent syntax:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-csharp" data-lang="csharp"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;Assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;That&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;zulu&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="n"&gt;Is&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;EqualTo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;Zulu&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is the &lt;em&gt;new&lt;/em&gt; fluent notation in NUnit (new and new&amp;hellip;. it has been around for a very long time now, at least since NUnit 2.4, and that is pretty far back in time).&lt;/p&gt;&#10;&lt;p&gt;But - converting from one to another is not fun. Doing this manually is a very boring task.&lt;/p&gt;&#10;&lt;p&gt;Enter the &lt;a href="https://github.com/nunit/nunit.analyzers"&gt;NUnit.Analyzers&lt;/a&gt;, a new set of Roslyn based analyzers with refactoring.&lt;/p&gt;</description></item><item><title>How to convert NUnit Assert.AreEqual to fluent Assert.That syntax easily</title><link>https://hermit.no/archive/2018-11-03-how-to-convert-nunit-assert-areequal-to-fluent-assert-that-syntax-easily/</link><pubDate>Sat, 03 Nov 2018 21:51:11 +0100</pubDate><guid>https://hermit.no/archive/2018-11-03-how-to-convert-nunit-assert-areequal-to-fluent-assert-that-syntax-easily/</guid><description>&lt;p&gt;Once upon a time it was declared that an Assert statement should have constraints given as AreEqual and AreNotEqual. Further it was declared that it should be written in the opposite way of how a developer will think, that is with the expected value first and the actual value last. Why this was made so, is still unclear.&lt;/p&gt;&#10;&lt;p&gt;And then we end up with tons of code like:&lt;/p&gt;&#10;&lt;p&gt;&lt;code&gt;Assert.AreEqual(&amp;ldquo;Zulu&amp;rdquo;, zulu.Name);&#10;Assert.AreEqual(&amp;ldquo;Z - Zulu&amp;rdquo;, zulu.Description);&#10;Assert.AreEqual(FlagType.Signal, zulu.Sort);&#10;Assert.AreEqual(0.7, zulu.AspectRatio);&lt;/code&gt;&lt;/p&gt;</description></item><item><title>How to extend the NUnit constraints</title><link>https://hermit.no/archive/2018-11-01-how-to-extend-the-nunit-constraints/</link><pubDate>Thu, 01 Nov 2018 02:19:54 +0100</pubDate><guid>https://hermit.no/archive/2018-11-01-how-to-extend-the-nunit-constraints/</guid><description>&lt;p&gt;&lt;a href="http://nunit.org/"&gt;NUnit&lt;/a&gt; has a very rich and readable constraint set.  Normally you don’t need to do anything. But, there are some cases where it would be nice to be able to tweak these constraints.  You can always wrap them and extend them that way, but then you lose all the other good stuff, like chaining.  What is not so well known is that you can extend the existing constraints, they are &lt;strong&gt;designed&lt;/strong&gt; to be extendable!   In this post I will show how you can do that easily.&lt;/p&gt;</description></item><item><title>VSIX based Test Adapters to be deprecated in Visual Studio for C# and Visual Basic to speed up testing</title><link>https://hermit.no/archive/2018-07-08-vsix-based-test-adapters-to-be-deprecated-in-visual-studio-for-c-and-visual-basic-to-speed-up-testing/</link><pubDate>Sun, 08 Jul 2018 13:16:14 +0100</pubDate><guid>https://hermit.no/archive/2018-07-08-vsix-based-test-adapters-to-be-deprecated-in-visual-studio-for-c-and-visual-basic-to-speed-up-testing/</guid><description>&lt;p&gt;Test Adapters come in two flavors, VSIX based and Nuget based. The VSIX based are installed as extensions to Visual Studio and therefore will apply to all solutions you load, The Nuget based adapter packages must be installed at least into one project in your solution and will only work for that solution.&lt;/p&gt;&#10;&lt;p&gt;All versions of Visual Studio have supported both flavors, but from &lt;strong&gt;Visual Studio 2017 Update 15.8 (Preview 4) the VSIX based adapters for C# and Visual Basic will be deprecated&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>A series of short recipes for VSTS, VISUAL STUDIO and NUnit</title><link>https://hermit.no/archive/2018-06-12-a-series-of-short-recipes-for-vsts-visual-studio-and-nunit/</link><pubDate>Tue, 12 Jun 2018 09:58:57 +0100</pubDate><guid>https://hermit.no/archive/2018-06-12-a-series-of-short-recipes-for-vsts-visual-studio-and-nunit/</guid><description>&lt;p&gt;I have had a need to have more easy access to information on how to do certain stuff, and have some easy access to simple code blocks, or templates, I can copy/paste.  A blog post is for me somewhat more extensive, and that format was not really suited for smaller notes.  So I decided to write them down as “recipes”, which is a small post, larger than a post-it, but smaller than a full blown blog post.&lt;/p&gt;</description></item><item><title>NUnit testing using the new project format</title><link>https://hermit.no/tricks/nunit-testing-using-the-new-project-format/</link><pubDate>Sun, 10 Jun 2018 16:38:00 +0100</pubDate><guid>https://hermit.no/tricks/nunit-testing-using-the-new-project-format/</guid><description>&lt;h1 id="nunit-testing-using-the-sdk-project-format"&gt;NUnit testing using the SDK project format&lt;/h1&gt;&#10;&lt;p&gt;This is a short recipe for how to set up your project for NUnit testing usign the SDK project format&lt;/p&gt;&#10;&lt;p&gt;Microsoft Visual Studio supports two project formats. The new format uses package references and are much simpler than the old one. It will also pick up any C# file in your folder, so you don&amp;rsquo;t need to add them explicitly.&lt;/p&gt;&#10;&lt;p&gt;All you need to do to use NUnit with the new format is as shown in the example csproj below. The target framework can be any of the .net framework ones. For information on using .net core, see &lt;a href="http://hermit.no/net-core-setup/"&gt;a short recipe for that&lt;/a&gt;&lt;/p&gt;</description></item><item><title>How to get NUnit3TestAdapter pre-release packages</title><link>https://hermit.no/nunit/get-nunit3testadapter-pre-release-packages/</link><pubDate>Tue, 06 Feb 2018 21:59:50 +0100</pubDate><guid>https://hermit.no/nunit/get-nunit3testadapter-pre-release-packages/</guid><description>&lt;h2 id="adapter-pre-releases"&gt;Adapter pre-releases&lt;/h2&gt;&#10;&lt;p&gt;We publish pre-release packages for every pull request merge to the master branch in the &lt;a href="https://github.com/nunit/nunit3-vs-adapter"&gt;NUnit3TestAdapter&lt;/a&gt; project. They are published to our &lt;a href="https://www.myget.org/F/nunit/api/v3/index.json"&gt;NUnit MyGet feed&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;Feed:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-csharp" data-lang="csharp"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;https&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="c1"&gt;//www.myget.org/F/nunit/api/v3/index.json&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Instructions for getting it for the different package tools, and also to see which is the latest version, go here:&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://www.myget.org/feed/nunit/package/nuget/NUnit3TestAdapter"&gt;NUnit3TestAdapter package page on MyGet&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;For NuGet (package.config)&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-csharp" data-lang="csharp"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;Install&lt;/span&gt;&lt;span class="p"&gt;-&lt;/span&gt;&lt;span class="n"&gt;Package&lt;/span&gt; &lt;span class="n"&gt;NUnit3TestAdapter&lt;/span&gt; &lt;span class="p"&gt;-&lt;/span&gt;&lt;span class="n"&gt;Version&lt;/span&gt; &lt;span class="m"&gt;3.10&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="m"&gt;0&lt;/span&gt;&lt;span class="p"&gt;-&lt;/span&gt;&lt;span class="n"&gt;dev&lt;/span&gt;&lt;span class="p"&gt;-&lt;/span&gt;&lt;span class="m"&gt;00702&lt;/span&gt; &lt;span class="p"&gt;-&lt;/span&gt;&lt;span class="n"&gt;Source&lt;/span&gt; &lt;span class="n"&gt;https&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="c1"&gt;//www.myget.org/F/nunit/api/v3/index.json&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For NuGet (PackageReference in csproj)&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-xml" data-lang="xml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;&amp;lt;PackageReference&lt;/span&gt; &lt;span class="na"&gt;Include=&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;NUnit3TestAdapter&amp;#34;&lt;/span&gt; &lt;span class="na"&gt;Version=&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;3.10.0-dev-00702&amp;#34;&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;strong&gt;Tip 1:&lt;/strong&gt; The PackageReference version requires you to have the feed URL in the nuget.config file.&lt;/p&gt;</description></item><item><title>How to resolve cases of Visual Studio &amp;ldquo;No tests appearing&amp;rdquo;</title><link>https://hermit.no/archive/2017-12-29-how-to-resolve-cases-of-visual-studio-no-tests-appearing/</link><pubDate>Fri, 29 Dec 2017 21:22:09 +0100</pubDate><guid>https://hermit.no/archive/2017-12-29-how-to-resolve-cases-of-visual-studio-no-tests-appearing/</guid><description>&lt;p&gt;The Visual Studio Test Explorer can be a bit picky about showing tests.  There are multiple reasons for why they don’t always show up when you expect them to do, and most of the cases are &lt;a href="https://en.wiktionary.org/wiki/PEBCAK"&gt;PEBKAC&lt;/a&gt; type of issues.  That doesn’t mean it is easy, there are just becoming too many variations, and Visual Studio does not tell you what is really wrong.&lt;/p&gt;&#10;&lt;p&gt;The different variations of targets and adapters doesn’t make this easier.  To help in diagnosing this, I have created the diagnostic flow chart shown below.   Further below you will find the comments for each block and how to rectify the issues, if you don’t already know.  The flowchart is mostly general, although I use NUnit as the default adapter in the examples.&lt;/p&gt;</description></item><item><title>WrapThat.System : Wrappers for system.io to simplify unit testing</title><link>https://hermit.no/archive/2017-04-22-wrapthat-system-wrappers-for-system-io-to-simplify-unit-testing/</link><pubDate>Sat, 22 Apr 2017 10:48:17 +0100</pubDate><guid>https://hermit.no/archive/2017-04-22-wrapthat-system-wrappers-for-system-io-to-simplify-unit-testing/</guid><description>&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;&#10;&lt;p&gt;You have all seen it, you have all done it: Written code using the static methods from the System.IO namespace for handling directories and files.   Or, you are maintaining legacy code where that usage is common in certain places.  And now the code is huge,  you have no unit tests, because unit testing classes that directly access the file system is just pain,  and the cost of a rewrite is too big.&lt;/p&gt;</description></item><item><title>Visual Studio 2015 and NUnit, with a little NuGet issue</title><link>https://hermit.no/archive/2014-11-14-visual-studio-2015-and-nunit-with-a-little-nuget-issue/</link><pubDate>Fri, 14 Nov 2014 14:20:52 +0100</pubDate><guid>https://hermit.no/archive/2014-11-14-visual-studio-2015-and-nunit-with-a-little-nuget-issue/</guid><description>&lt;p&gt;&lt;font size="2" face="Segoe UI"&gt;&lt;strong&gt;NUGET&lt;/strong&gt;&lt;/font&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;font size="2" face="Segoe UI"&gt;The current version 1.2 of the NuGet adapters for NUnit works with the VS 2015 Preview (and earlier CTPs).  &lt;/font&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;font size="2" face="Segoe UI"&gt;You can find them here:  &lt;/font&gt;&lt;a href="http://www.nuget.org/packages/NUnitTestAdapter/"&gt;http://www.nuget.org/packages/NUnitTestAdapter/&lt;/a&gt;&lt;font size="2" face="Segoe UI"&gt;  and with framework: &lt;/font&gt;&lt;a href="http://www.nuget.org/packages/NUnitTestAdapter.WithFramework/"&gt;http://www.nuget.org/packages/NUnitTestAdapter.WithFramework/&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;font size="2" face="Segoe UI"&gt;Add one of these to your solution and it works without having the VSIX installed, both for VS2015 and for TFS build, including VSO build.  Note that you only need to add one of these to one of your projects in the solution.  &lt;/font&gt;&lt;/p&gt;</description></item><item><title>Fix for the &amp;lsquo;Could not find test executor&amp;rsquo; issue with NUnit, XUnit and Chutzpah when using ReSharper in Visual Studio</title><link>https://hermit.no/archive/2014-02-09-fix-for-the-lsquo-could-not-find-test-executor-rsquo-issue-with-nunit-xunit-and-chutzpah-when-using-resharper-in-visual-studio/</link><pubDate>Sun, 09 Feb 2014 00:25:00 +0100</pubDate><guid>https://hermit.no/archive/2014-02-09-fix-for-the-lsquo-could-not-find-test-executor-rsquo-issue-with-nunit-xunit-and-chutzpah-when-using-resharper-in-visual-studio/</guid><description>&lt;p&gt;This issue is resolved in the latest ReSharper release, version 8.2.0.2160, &lt;a href="http://www.jetbrains.com/resharper/download/"&gt;download here&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;The issue appears when using the Test Explorer to run tests in any of the frameworks mentioned in the title.  The tests are shown in the Test Explorer, but are not executed.  It may look like this:&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://gwb.blob.core.windows.net/terje/Windows-Live-Writer/Fix-for-the_14BC8/image_8.png"&gt;&lt;img src="../../images/2015/08/GWB-Windows-Live-Writer-Fix-for-the_14BC8-image_thumb_3.png" alt="image" title="image"&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Note:  The tests shown dimmed are NUnit and XUnit tests, which have the issue. The other tests are MSTests, which are not affected. The tests are discovered by the adapter, but not executed.&lt;/p&gt;</description></item></channel></rss>