<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com - Stories tagged with Testing</title>
    <description>the latest stories tagged with 'Testing' 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>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>Sat, 11 Feb 2012 20:24:16 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>Coded UI Tests : Property "ReadOnly" cannot be retrieved ...</title>
      <description>Did you ever encounter this error while trying to retrieve a property value from an AutomationElement ? I did !

Don't worry, there is always a work-around, and I've found one.

In this post, we'll dig a little more into this issue and give a little example of the "Coded UI Tests" fun  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.jonathanantoine.com%2f2012%2f01%2f10%2fcoded-ui-tests-property-readonly-cannot-be-retrieved-due-to-the-current-state-of-edit%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.jonathanantoine.com%2f2012%2f01%2f10%2fcoded-ui-tests-property-readonly-cannot-be-retrieved-due-to-the-current-state-of-edit%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Coded_UI_Tests_Property_ReadOnly_cannot_be_retrieved</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Coded_UI_Tests_Property_ReadOnly_cannot_be_retrieved</guid>
      <pubDate>Tue, 10 Jan 2012 19:04:29 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>Status Update on SpecsFor.Mvc</title>
      <description>SpecsFor.Mvc is an integration testing framework for ASP.NET MVC applications.  It enables you to write integration tests that are strongly-typed, refactor-friendly, and that run under the testing framework of your choice, all while leveraging your existing unit test writing skills.  

SpecsFor.Mvc is a work-in-progress, so please take a moment to give me some feedback on how the API is shaping up. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2fStatus-Update-on-SpecsForMvc.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2fStatus-Update-on-SpecsForMvc.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Status_Update_on_SpecsFor_Mvc</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Status_Update_on_SpecsFor_Mvc</guid>
      <pubDate>Mon, 02 Jan 2012 04:07:04 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>Generate Return Values Using Lambdas in Moq</title>
      <description>Mock objects and stubs created using the Moq framework are generally used to inject dependencies with expectations that define fixed results. For more complex scenarios, lambda expressions can be used to generate results based on provided arguments. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.blackwasp.co.uk%2fMoqReturnLambda.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.blackwasp.co.uk%2fMoqReturnLambda.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Generate_Return_Values_Using_Lambdas_in_Moq</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Generate_Return_Values_Using_Lambdas_in_Moq</guid>
      <pubDate>Thu, 22 Dec 2011 16:56:56 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>
    <item>
      <title>Web Testing with MbUnit and WatiN: Testing Asynchronous AJAX calls</title>
      <description>Concluding his look at combining MbUnit and Watin to produce clean web integration tests, Yann Trevin looks at testing asynchronous calls &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.developerfusion.com%2farticle%2f134437%2fweb-testing-with-mbunit-and-watin-part-3-testing-asynchronous-ajax-calls%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.developerfusion.com%2farticle%2f134437%2fweb-testing-with-mbunit-and-watin-part-3-testing-asynchronous-ajax-calls%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Web_Testing_with_MbUnit_and_WatiN_Testing_Asynchronous_AJAX_calls</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Web_Testing_with_MbUnit_and_WatiN_Testing_Asynchronous_AJAX_calls</guid>
      <pubDate>Wed, 14 Dec 2011 19:39:41 GMT</pubDate>
    </item>
    <item>
      <title>SpecsFor.com Launched, SpecsFor 2.2 Released!</title>
      <description>I'm pleased to announce that SpecsFor.com is now live.  I've also shipped a new version of SpecsFor that simplifies the painful task of creating multiple mocks of the same type for injection into IEnumerable parameters. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2fSpecsForcom-Launched-SpecsFor-22-Released!.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2fSpecsForcom-Launched-SpecsFor-22-Released!.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/SpecsFor_com_Launched_SpecsFor_2_2_Released</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/SpecsFor_com_Launched_SpecsFor_2_2_Released</guid>
      <pubDate>Mon, 12 Dec 2011 06:25:35 GMT</pubDate>
    </item>
    <item>
      <title>Using QUnit with ASP.NET MVC Razor Layouts</title>
      <description>QUnit is a Javascript unit testing framework. The post explains how to use QUnit with ASP.NET MVC Razor Layout. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fhaacked.com%2farchive%2f2011%2f12%2f10%2fusing-qunit-with-razor-layouts.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fhaacked.com%2farchive%2f2011%2f12%2f10%2fusing-qunit-with-razor-layouts.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Using_QUnit_with_ASP_NET_MVC_Razor_Layouts</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Using_QUnit_with_ASP_NET_MVC_Razor_Layouts</guid>
      <pubDate>Mon, 12 Dec 2011 06:25:35 GMT</pubDate>
    </item>
    <item>
      <title>Unit Testing Http Handlers and Auto Mocking with the Testable Pattern</title>
      <description>This post first describes how to implement IHttpHandler in a test friendly way and then moves on to a tutorial on Dependency Injection, the Testable pattern and Auto Mocking  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.mattwrock.com%2fpost%2f2011%2f12%2f07%2fUnit-Testing-ASPNet-Http-Handlers-and-a-discussion-of-Auto-Mocking-and-the-Testable-pattern.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.mattwrock.com%2fpost%2f2011%2f12%2f07%2fUnit-Testing-ASPNet-Http-Handlers-and-a-discussion-of-Auto-Mocking-and-the-Testable-pattern.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Unit_Testing_Http_Handlers_and_Auto_Mocking_with_the_Testable_Pattern</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Unit_Testing_Http_Handlers_and_Auto_Mocking_with_the_Testable_Pattern</guid>
      <pubDate>Wed, 07 Dec 2011 16:41:28 GMT</pubDate>
    </item>
    <item>
      <title>Two Things to Make Testing Fun</title>
      <description>How many of you actually enjoy writing tests, probably not a lot, right? Even though you know testing is important.  For some of us, it just doesn't feel right to spend time on creating tests than working on our world class application. I will not argue the merits of testing here, but I will tell you two things that will make testing fun: &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2ffutureofcoding.com%2ftwo-things-to-make-testing-fun%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2ffutureofcoding.com%2ftwo-things-to-make-testing-fun%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Two_Things_to_Make_Testing_Fun</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Two_Things_to_Make_Testing_Fun</guid>
      <pubDate>Wed, 30 Nov 2011 23:46:14 GMT</pubDate>
    </item>
    <item>
      <title>SpecsFor 2.0 Released!</title>
      <description>The newest version of the SpecsFor behavior-driven development framework is out with additional functionality to eliminate common points of testing friction. With a single NuGet package, you now have everything you need to start writing clean test cases. Read on to see how much easier writing tests could be. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2fSpecsFor-20-Released!.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2fSpecsFor-20-Released!.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/SpecsFor_2_0_Released</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/SpecsFor_2_0_Released</guid>
      <pubDate>Tue, 29 Nov 2011 14:24:31 GMT</pubDate>
    </item>
    <item>
      <title>Chutzpah 1.3.0 Released</title>
      <description>A new release of Chutzpah - A JavaScript test runner. This release adds support for the Jasmine test framework. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fmatthewmanela.com%2fblog%2fchutzpah-1-3-0-released%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fmatthewmanela.com%2fblog%2fchutzpah-1-3-0-released%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Chutzpah_1_3_0_Released</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Chutzpah_1_3_0_Released</guid>
      <pubDate>Sat, 19 Nov 2011 22:35:59 GMT</pubDate>
    </item>
    <item>
      <title>the recorder encountered a wrong control while recording the last acti</title>
      <description>One more quick post on Coded UI tests recording issue. Today, the coded UI test builder tool said to me "The recorder encountered a wrong control while recording the last action." !

After some search in my app, I found out that it'is related to a ScrollViewer in a TabControl.

In this post we'll see how I solved it. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.jonathanantoine.com%2f2011%2f11%2f15%2fcoded-ui-tests-the-recorder-encountered-a-wrong-control-while-recording-the-last-action%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.jonathanantoine.com%2f2011%2f11%2f15%2fcoded-ui-tests-the-recorder-encountered-a-wrong-control-while-recording-the-last-action%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/the_recorder_encountered_a_wrong_control_while_recording_the_last_acti</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/the_recorder_encountered_a_wrong_control_while_recording_the_last_acti</guid>
      <pubDate>Thu, 17 Nov 2011 10:00:08 GMT</pubDate>
    </item>
    <item>
      <title>Testing Entity Framework Applications - Part 2</title>
      <description>In part 2 of this series by Thomas Weller, he shows us how to mock test data using the commercial TypeMock library. In his next article, he will show how the same can be achieved using the free ndbunit library. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fgeekswithblogs.net%2fthomasweller%2farchive%2f2011%2f11%2f08%2ftesting-entity-framework-applications-pt.-2-typemock.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fgeekswithblogs.net%2fthomasweller%2farchive%2f2011%2f11%2f08%2ftesting-entity-framework-applications-pt.-2-typemock.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Testing_Entity_Framework_Applications_Part_2</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Testing_Entity_Framework_Applications_Part_2</guid>
      <pubDate>Wed, 09 Nov 2011 15:58:34 GMT</pubDate>
    </item>
    <item>
      <title>Testing Entity Framework Applications - Part 1</title>
      <description>Thomas Weller walks us through some of the issues with writing integration tests for applications using Entity Framework, and offers up some solutions for stubbing the data layer. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fgeekswithblogs.net%2fthomasweller%2farchive%2f2011%2f11%2f06%2ftesting-entity-framework-applications-pt.-1.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fgeekswithblogs.net%2fthomasweller%2farchive%2f2011%2f11%2f06%2ftesting-entity-framework-applications-pt.-1.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Testing_Entity_Framework_Applications_Part_1</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Testing_Entity_Framework_Applications_Part_1</guid>
      <pubDate>Wed, 09 Nov 2011 15:58:34 GMT</pubDate>
    </item>
  </channel>
</rss>
