<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com - published unittesting stories</title>
    <description>the latest published unittesting stories from DotNetKicks.com</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>Noninvasive Unit Testing in ASP.NET MVC4 - A Microsoft Fakes Deep Dive</title>
      <description>A lot of today's unit testing technologies require significant invasive code changes in order to unit test appropriately. In this post Microsoft Fakes in VS11 is used to apply noninvasive testing techniques to test a default &amp;quot;Internet Application&amp;quot; MVC 4 project making absolutely no code changes at all. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.richonsoftware.com%2fpost%2f2012%2f05%2f02%2fNoninvasive-Unit-Testing-in-ASPNET-MVC-A-Microsoft-Fakes-Deep-Dive.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.richonsoftware.com%2fpost%2f2012%2f05%2f02%2fNoninvasive-Unit-Testing-in-ASPNET-MVC-A-Microsoft-Fakes-Deep-Dive.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Noninvasive_Unit_Testing_in_ASP_NET_MVC4_A_Microsoft_Fakes_Deep_Dive</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Noninvasive_Unit_Testing_in_ASP_NET_MVC4_A_Microsoft_Fakes_Deep_Dive</guid>
      <pubDate>Fri, 18 May 2012 13:33:21 GMT</pubDate>
    </item>
    <item>
      <title>Using Shims in Visual Studio 11 to test untestable code.</title>
      <description>New upcoming version of Visual Studio, codename VisualStudio11 contains a library to isolate call to static and non-virtual function to simply testing of classes written without unit testing in mind. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.codewrecks.com%2fblog%2findex.php%2f2012%2f04%2f27%2fusing-shims-in-visual-studio-11-to-test-untestable-code%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.codewrecks.com%2fblog%2findex.php%2f2012%2f04%2f27%2fusing-shims-in-visual-studio-11-to-test-untestable-code%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Using_Shims_in_Visual_Studio_11_to_test_untestable_code</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Using_Shims_in_Visual_Studio_11_to_test_untestable_code</guid>
      <pubDate>Mon, 30 Apr 2012 14:39:52 GMT</pubDate>
    </item>
    <item>
      <title>Running multiple browsers in one test run with Selenium</title>
      <description>The beauty of Selenium is that it allows you to test your UI against all of the common browsers out there at the moment. Writing the code to test for a test scenario is quick and easy and getting up and running with Selenium can be done in a matter of minutes. Selenium works alongside Nunit and also nicely slots in with your automated build environment. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdeanhume.com%2fHome%2fBlogPost%2frunning-multiple-browsers-in-one-test-run-with-selenium%2f70"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdeanhume.com%2fHome%2fBlogPost%2frunning-multiple-browsers-in-one-test-run-with-selenium%2f70" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Running_multiple_browsers_in_one_test_run_with_Selenium</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Running_multiple_browsers_in_one_test_run_with_Selenium</guid>
      <pubDate>Thu, 26 Apr 2012 13:54:16 GMT</pubDate>
    </item>
    <item>
      <title>Comparing Microsoft Moles in VS2010 to Microsoft Fakes in VS11</title>
      <description>Provides a detailed comparison between Microsoft Moles in VS10 and Microsoft Fakes in VS11 in regards to using Moles for "future proofing" new testing initiatives and perhaps to bridge the gap between today's testing and tomorrow's tools. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.richonsoftware.com%2fpost%2f2012%2f04%2f20%2fComparing-Microsoft-Moles-in-Visual-Studio-2010-to-Microsoft-Fakes-in-Visual-Studio-11.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.richonsoftware.com%2fpost%2f2012%2f04%2f20%2fComparing-Microsoft-Moles-in-Visual-Studio-2010-to-Microsoft-Fakes-in-Visual-Studio-11.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Comparing_Microsoft_Moles_in_VS2010_to_Microsoft_Fakes_in_VS11</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Comparing_Microsoft_Moles_in_VS2010_to_Microsoft_Fakes_in_VS11</guid>
      <pubDate>Mon, 23 Apr 2012 14:56:11 GMT</pubDate>
    </item>
    <item>
      <title>Writing integration tests for ASP .NET with Selenium 2.0 - Part 2</title>
      <description>This is the second in a series of posts on writing integration tests for ASP .NET using the Selenium 2.0 web application testing system.

In this post, I'll go over how to write and run C# test-cases using Selenium 2.0. I've also provided a base-class that contains helper methods for repetitive stuff like typing inside input fields. The base-class also speeds up the tests by re-using the same driver and preserving logins across tests. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fnizarnoorani.com%2fwriting-integration-tests-for-asp-net-with-selenium-2-0-part-2"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fnizarnoorani.com%2fwriting-integration-tests-for-asp-net-with-selenium-2-0-part-2" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Writing_integration_tests_for_ASP_NET_with_Selenium_2_0_Part_2</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Writing_integration_tests_for_ASP_NET_with_Selenium_2_0_Part_2</guid>
      <pubDate>Tue, 17 Apr 2012 07:36:27 GMT</pubDate>
    </item>
    <item>
      <title>Using Stubs and Shims to Test with Microsoft Fakes in Visual Studio 11</title>
      <description>Microsoft has released Microsoft Fakes, a full featured mocking framework built into Visual Studio 11, which can &amp;quot;shim&amp;quot; any .NET method, including non-virtual and static methods in sealed types.  This post digs into those features a little deeper and their general implications. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.richonsoftware.com%2fpost%2f2012%2f04%2f05%2fUsing-Stubs-and-Shim-to-Test-with-Microsoft-Fakes-in-Visual-Studio-11.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.richonsoftware.com%2fpost%2f2012%2f04%2f05%2fUsing-Stubs-and-Shim-to-Test-with-Microsoft-Fakes-in-Visual-Studio-11.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Using_Stubs_and_Shims_to_Test_with_Microsoft_Fakes_in_Visual_Studio_11</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Using_Stubs_and_Shims_to_Test_with_Microsoft_Fakes_in_Visual_Studio_11</guid>
      <pubDate>Thu, 12 Apr 2012 20:53:26 GMT</pubDate>
    </item>
    <item>
      <title>Writing integration tests for ASP .NET with Selenium - Part 1</title>
      <description>The first in a series of blog posts that will discuss how to setup, configure and write integration tests for ASP .NET using Selenium. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fnizarnoorani.com%2fwriting-integration-tests-for-asp-net-with-selenium-part-1"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fnizarnoorani.com%2fwriting-integration-tests-for-asp-net-with-selenium-part-1" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Writing_integration_tests_for_ASP_NET_with_Selenium_Part_1</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Writing_integration_tests_for_ASP_NET_with_Selenium_Part_1</guid>
      <pubDate>Thu, 12 Apr 2012 06:24:19 GMT</pubDate>
    </item>
    <item>
      <title>Migrating from NUnit to xUnit</title>
      <description>If you are currently using NUnit to write your unit tests, then it is not at all difficult to migrate to using xUnit. The philosophical difference between the two is simply this: with xUnit you need to think of your tests as objects, rather than of methods. Here is a visual representation of equivalent test setups between NUnit and xUnit... &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.tomdupont.net%2f2012%2f04%2fmigrating-from-nunit-to-xunit.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.tomdupont.net%2f2012%2f04%2fmigrating-from-nunit-to-xunit.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Migrating_from_NUnit_to_xUnit</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Migrating_from_NUnit_to_xUnit</guid>
      <pubDate>Mon, 09 Apr 2012 01:55:05 GMT</pubDate>
    </item>
    <item>
      <title>From Legacy to Dependency Injection</title>
      <description>We've all encountered tightly-bound code, and our first instinct is to correct it. However, there are only so many hours in a sprint, and it's not always convenient to go on a large refactoring spree when the backlog is filling up. With JustMock, you can still ensure the code works, and it will set you up for the cleaning that will take place at a ... &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblogs.telerik.com%2fblogs%2fposts%2f12-04-04%2ffrom-legacy-to-dependency-injection.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblogs.telerik.com%2fblogs%2fposts%2f12-04-04%2ffrom-legacy-to-dependency-injection.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/From_Legacy_to_Dependency_Injection</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/From_Legacy_to_Dependency_Injection</guid>
      <pubDate>Fri, 06 Apr 2012 00:53:32 GMT</pubDate>
    </item>
    <item>
      <title>Test-Driven and Test-First Development &amp;#187; Noam Kfir</title>
      <description>A description of the essence of TDD, and why you can write tests after code and still call it TDD. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fnoam.kfir.cc%2fblog%2f2012%2f03%2f10%2ftest-driven-and-test-first-development%3fppt%3dc095cc734be521cd8f484d7c43fababf"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fnoam.kfir.cc%2fblog%2f2012%2f03%2f10%2ftest-driven-and-test-first-development%3fppt%3dc095cc734be521cd8f484d7c43fababf" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Test_Driven_and_Test_First_Development_Noam_Kfir</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Test_Driven_and_Test_First_Development_Noam_Kfir</guid>
      <pubDate>Mon, 19 Mar 2012 16:39:14 GMT</pubDate>
    </item>
    <item>
      <title>Customizing Project Level Templates in Visual Studio Unit Test Framewo</title>
      <description>The Visual Studio Unit Test framework is the only test framework provided out of the box with ASP.NET MVC 3. This article shows you how to create and install custom test project templates and view engine options. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.dotnet-tv.com%2f2012%2f03%2f12%2fcustomizing-project-level-templates-in-visual-studio-unit-test-framework%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.dotnet-tv.com%2f2012%2f03%2f12%2fcustomizing-project-level-templates-in-visual-studio-unit-test-framework%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Customizing_Project_Level_Templates_in_Visual_Studio_Unit_Test_Framewo</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Customizing_Project_Level_Templates_in_Visual_Studio_Unit_Test_Framewo</guid>
      <pubDate>Thu, 15 Mar 2012 12:34:54 GMT</pubDate>
    </item>
    <item>
      <title>How to mock DateTime.Now in unit tests</title>
      <description>Different ways to mock DateTime.Now in unit tests &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcatchblock.com%2fblog%2fpost%2f2012%2f03%2f05%2fHow-to-mock-DateTimeNow-in-unit-tests.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcatchblock.com%2fblog%2fpost%2f2012%2f03%2f05%2fHow-to-mock-DateTimeNow-in-unit-tests.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/How_to_mock_DateTime_Now_in_unit_tests</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/How_to_mock_DateTime_Now_in_unit_tests</guid>
      <pubDate>Tue, 06 Mar 2012 20:05:30 GMT</pubDate>
    </item>
    <item>
      <title>JustCode and QUnit means easy JavaScript unit testing in Visual Studio</title>
      <description>As we showed in the Jasmine blog postJustCode provides seamless integration of JavaScript unit testing inside Visual Studio. JustCode supports two of the most widely used JavaScript unit testing frameworks - Jasmine and QUnit, allowing you to leverage the one that better fits your needs or both. Today's post covers the support of QUnit JavaScript unit tests in JustCode. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblogs.telerik.com%2fjustteam%2fposts%2f12-02-29%2fjustcode-and-qunit-means-easy-javascript-unit-testing-in-visual-studio.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblogs.telerik.com%2fjustteam%2fposts%2f12-02-29%2fjustcode-and-qunit-means-easy-javascript-unit-testing-in-visual-studio.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/JustCode_and_QUnit_means_easy_JavaScript_unit_testing_in_Visual_Studio</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/JustCode_and_QUnit_means_easy_JavaScript_unit_testing_in_Visual_Studio</guid>
      <pubDate>Thu, 01 Mar 2012 20:10:07 GMT</pubDate>
    </item>
    <item>
      <title>Sharing a WebDriver across TestFixtures</title>
      <description>WebDriver (also known as Selenium 2.0) is a web testing tool that is both useful and easy, which is a very rare find. If you are doing web development with ASP.NET, you need to take 30 minutes of your time and go try out WebDriver. That is all the time it will take to get you hooked.

To launch a browser you need only new up a Driver object for that browser. I used to create a new Driver in my TestFixtureSetup, and then close and dispose of that in the testFixtureTearDown. However now that Firefox does not persist my windows login credentials it can be very frustrating to have to log back in for every test fixture.

A solution to this problem is simply to share a single WebDriver across multiple TestFixtures. Fortunately NUnit's SetUpFixture makes this very easy to do. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.tomdupont.net%2f2012%2f02%2fsharing-webdriver-across-testfixtures.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.tomdupont.net%2f2012%2f02%2fsharing-webdriver-across-testfixtures.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Sharing_a_WebDriver_across_TestFixtures</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Sharing_a_WebDriver_across_TestFixtures</guid>
      <pubDate>Mon, 13 Feb 2012 15:16:34 GMT</pubDate>
    </item>
    <item>
      <title>NCrunch</title>
      <description>Not so often, but every once in a while a new great development tool comes around. This is one of those times. Meet NCrunch. A TDD tool that will speed up your way of doing unit tests &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fgeeklyeverafter.blogspot.com%2f2012%2f02%2fncrunch.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fgeeklyeverafter.blogspot.com%2f2012%2f02%2fncrunch.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/NCrunch</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/NCrunch</guid>
      <pubDate>Fri, 10 Feb 2012 08:29:16 GMT</pubDate>
    </item>
    <item>
      <title>Testing DI bootstrappers</title>
      <description>While your Dependency Injection bootstrappers - being responsible for gluing your application together - are a vital part of your application, they are seldom put under test. I don't see any reason why they shouldn't be though. The cost of these tests is negligible, definitely if you compare it to the cost of the often catastrophical outcome of bugs in your bootstrappers. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fjclaes.blogspot.com%2f2012%2f02%2ftesting-di-bootstrappers.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fjclaes.blogspot.com%2f2012%2f02%2ftesting-di-bootstrappers.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Testing_DI_bootstrappers</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Testing_DI_bootstrappers</guid>
      <pubDate>Mon, 06 Feb 2012 19:10:13 GMT</pubDate>
    </item>
    <item>
      <title>New tools for your TDD arsenal</title>
      <description>Alexander Beletsky shares a list of sweet new TDD tools to retrofit into your current load-out, including a tool to automatically re-run tests as you make changes to source code, a replacement for Moq, and some awesome fluent assertions. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.beletsky.net%2f2012%2f02%2fnew-tools-in-my-tdd-arsenal.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.beletsky.net%2f2012%2f02%2fnew-tools-in-my-tdd-arsenal.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/New_tools_for_your_TDD_arsenal</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/New_tools_for_your_TDD_arsenal</guid>
      <pubDate>Fri, 03 Feb 2012 19:42:19 GMT</pubDate>
    </item>
    <item>
      <title>Guilt Driven Development</title>
      <description>Do you want to use Test Driven Development in your daily work but lack the necessary motivation? Do you have the nagging feeling that TDD could use more nagging to make you get things done?

If this describes you, then you should definitely consider Guilt Driven Development. GDD is a powerful new technique based on one of the strongest motivating forces known to man: guilt. It works by forcing you to create promises to it and then guilts you into keeping them. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2ftatiyants.com%2fguilt-driven-development%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2ftatiyants.com%2fguilt-driven-development%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Guilt_Driven_Development</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Guilt_Driven_Development</guid>
      <pubDate>Thu, 12 Jan 2012 14:59:32 GMT</pubDate>
    </item>
    <item>
      <title>Story in bddify </title>
      <description>Mehdi Khalili continues his series looking at the use of bddify, the simple to use and extend BDD framework for .Net developers. In this part Mehdi looks at how you can introduce the concept of a story into your behaviour tests. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.mehdi-khalili.com%2fbddify-in-action%2fstory"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.mehdi-khalili.com%2fbddify-in-action%2fstory" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Story_in_bddify</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Story_in_bddify</guid>
      <pubDate>Tue, 03 Jan 2012 21:01:55 GMT</pubDate>
    </item>
    <item>
      <title>Static Code Analysis</title>
      <description>The most important thing I have done as a programmer in recent years is to aggressively pursue static code analysis.  Even more valuable than the hundreds of serious bugs I have prevented with it is the change in mindset about the way I view software reliability and code quality. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2faltdevblogaday.com%2f2011%2f12%2f24%2fstatic-code-analysis%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2faltdevblogaday.com%2f2011%2f12%2f24%2fstatic-code-analysis%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Static_Code_Analysis</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Static_Code_Analysis</guid>
      <pubDate>Tue, 03 Jan 2012 16:52:27 GMT</pubDate>
    </item>
    <item>
      <title>Method name conventions in bddify</title>
      <description>Mehdi Khalili continues his series looking in detail at his bddify framework. This part explores the naming and structure of your tests, and the two different ways (reflective and fluent) of reading scenarios. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.mehdi-khalili.com%2fbddify-in-action%2fmethod-name-conventions"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.mehdi-khalili.com%2fbddify-in-action%2fmethod-name-conventions" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Method_name_conventions_in_bddify</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Method_name_conventions_in_bddify</guid>
      <pubDate>Mon, 02 Jan 2012 14:51:28 GMT</pubDate>
    </item>
    <item>
      <title>Assert on number and text of Nhibernate queries during a unit test</title>
      <description>A test helper class that permits me to assert on the number and text of the query that Nhibernate issued to the database during the test &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.codewrecks.com%2fblog%2findex.php%2f2011%2f12%2f30%2funit-test-nhibernate-query-to-verify-n1%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.codewrecks.com%2fblog%2findex.php%2f2011%2f12%2f30%2funit-test-nhibernate-query-to-verify-n1%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Assert_on_number_and_text_of_Nhibernate_queries_during_a_unit_test</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Assert_on_number_and_text_of_Nhibernate_queries_during_a_unit_test</guid>
      <pubDate>Fri, 30 Dec 2011 15:38:28 GMT</pubDate>
    </item>
    <item>
      <title>Introduction to bddify</title>
      <description>Mehdi Khalili announces the release of bddify 1.0, a BDD testing framework which makes it easy to turn Arrange Act Assert unit test into BDD tests, and kicks off a series of posts looking at the framework, starting with an introduction to its history and use. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.mehdi-khalili.com%2fbddify-in-action%2fintroduction"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.mehdi-khalili.com%2fbddify-in-action%2fintroduction" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Introduction_to_bddify</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Introduction_to_bddify</guid>
      <pubDate>Wed, 28 Dec 2011 15:54:28 GMT</pubDate>
    </item>
    <item>
      <title>You write too many tests and open too many bugs</title>
      <description>Microsoft's Liam Price shares his thoughts on the problems associated with writing too many tests as well as with testers opening too many bugs. Seems like another case of &amp;quot;less is more&amp;quot;, when it comes to testing. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblogs.msdn.com%2fb%2fwltester%2farchive%2f2011%2f12%2f20%2fyou-write-too-many-tests-and-open-too-many-bugs.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblogs.msdn.com%2fb%2fwltester%2farchive%2f2011%2f12%2f20%2fyou-write-too-many-tests-and-open-too-many-bugs.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/You_write_too_many_tests_and_open_too_many_bugs</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/You_write_too_many_tests_and_open_too_many_bugs</guid>
      <pubDate>Thu, 22 Dec 2011 15:00:30 GMT</pubDate>
    </item>
    <item>
      <title>Just because you can test it, doesn't mean you should</title>
      <description>Samson Tanrena shares his thoughts on why choosing what to test, rather than simply testing all code, is an important step in shipping your product. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblogs.msdn.com%2fb%2fwltester%2farchive%2f2011%2f12%2f13%2fjust-because-you-can-test-it-doesn-t-mean-you-should.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblogs.msdn.com%2fb%2fwltester%2farchive%2f2011%2f12%2f13%2fjust-because-you-can-test-it-doesn-t-mean-you-should.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Just_because_you_can_test_it_doesn_t_mean_you_should</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Just_because_you_can_test_it_doesn_t_mean_you_should</guid>
      <pubDate>Thu, 15 Dec 2011 15:15:19 GMT</pubDate>
    </item>
  </channel>
</rss>
