<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com - Stories tagged with TDD</title>
    <description>the latest stories tagged with 'TDD' 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>Code Focused Development in Visual Studio 2010</title>
      <description>&amp;quot;In a blog post in November, I mentioned a feature called "Quick Search" - one of the code focused features of Visual Studio 2010.  We have been lagging behind some in this area in the past and we wanted to focus on this as a key pillar for Visual Studio 2010.  Today, I'd like to share some more details of our code focused development investments and features. &amp;quot; &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblogs.msdn.com%2fsomasegar%2farchive%2f2008%2f12%2f19%2fcode-focused-development-in-vs-2010.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblogs.msdn.com%2fsomasegar%2farchive%2f2008%2f12%2f19%2fcode-focused-development-in-vs-2010.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/visualstudio/Code_Focused_Development_in_Visual_Studio_2010</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/visualstudio/Code_Focused_Development_in_Visual_Studio_2010</guid>
      <pubDate>Mon, 29 Dec 2008 12:36:41 GMT</pubDate>
    </item>
    <item>
      <title>Dear PowerShell Santa...</title>
      <description>PowerShell has a great potential, but it needs professional tool support in order for it to mature. The current solutions are far too amateur. Here is my list of PowerShell improvements for Santa Claus &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.tellingmachine.com%2fpost%2f2008%2f12%2fDear-PowerShell-Santa.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.tellingmachine.com%2fpost%2f2008%2f12%2fDear-PowerShell-Santa.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Dear_PowerShell_Santa</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Dear_PowerShell_Santa</guid>
      <pubDate>Wed, 17 Dec 2008 07:13:43 GMT</pubDate>
    </item>
    <item>
      <title>Experimental study about Test Driven Development</title>
      <description>We talk with him about Test Driven Development: Does it work better? How better? What's the catch?
To answer these questions, Nachi talks about a study done over multiple teams within and outside of Microsoft on TDD. The results are very interesting, as they are based on real teams with real products, so I definitely encourage you to watch the video or download the paper to grok the numbers in details. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fchannel9.msdn.com%2fposts%2fPeli%2fExperimental-study-about-Test-Driven-Development%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fchannel9.msdn.com%2fposts%2fPeli%2fExperimental-study-about-Test-Driven-Development%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Experimental_study_about_Test_Driven_Development</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Experimental_study_about_Test_Driven_Development</guid>
      <pubDate>Wed, 10 Dec 2008 15:50:59 GMT</pubDate>
    </item>
    <item>
      <title>Tutorial to TDD using Rhino Mocks and SystemWrapper.</title>
      <description>Learn how to do TDD and mocking.  Also discover new library SystemWrapper. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fvkreynin.wordpress.com%2f2008%2f12%2f04%2ftutorial-to-tdd-using-rhino-mocks-and-systemwrapper%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fvkreynin.wordpress.com%2f2008%2f12%2f04%2ftutorial-to-tdd-using-rhino-mocks-and-systemwrapper%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Tutorial_to_TDD_using_Rhino_Mocks_and_SystemWrapper</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Tutorial_to_TDD_using_Rhino_Mocks_and_SystemWrapper</guid>
      <pubDate>Fri, 05 Dec 2008 00:26:48 GMT</pubDate>
    </item>
    <item>
      <title>Code Contracts - TDD in a DbC World </title>
      <description>As developers start to discover the upcoming Code Contracts for .NET 4.0, it's important to understand not only Design by Contract, and TDD, but how they can complement each other.  For business value, we as developers need to flush out our design through the use of TDD, and we can refactor into using contracts for our constraints over time.  With these methodologies in place, the edge cases will melt away and help us ensure DRY and write more concise code directly having business value. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcodebetter.com%2fblogs%2fmatthew.podwysocki%2farchive%2f2008%2f11%2f25%2fcode-contracts-dbc-in-a-tdd-world.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcodebetter.com%2fblogs%2fmatthew.podwysocki%2farchive%2f2008%2f11%2f25%2fcode-contracts-dbc-in-a-tdd-world.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Code_Contracts_TDD_in_a_DbC_World</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Code_Contracts_TDD_in_a_DbC_World</guid>
      <pubDate>Thu, 27 Nov 2008 09:36:13 GMT</pubDate>
    </item>
    <item>
      <title>Crazy Talk: Reducing ORM Friction</title>
      <description>Let's get this out of the way: I know you're going to think I'm nuts as you read this. You may &amp;quot;pfft&amp;quot; to what you're about to read - know that I know you're &amp;quot;pfft&amp;quot;-ing me. All I ask is that you consider what I'm about to suggest... &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.wekeroad.com%2fblog%2fcrazy-talk-reducing-orm-friction%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.wekeroad.com%2fblog%2fcrazy-talk-reducing-orm-friction%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/Crazy_Talk_Reducing_ORM_Friction</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/Crazy_Talk_Reducing_ORM_Friction</guid>
      <pubDate>Sun, 16 Nov 2008 03:01:12 GMT</pubDate>
    </item>
    <item>
      <title>Acceptance TDD Explained</title>
      <description>Acceptance test-driven development is what helps developers build high-quality software that fulfills the business's needs as reliably as TDD helps ensure the software's technical quality. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.methodsandtools.com%2farchive%2farchive.php%3fid%3d72"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.methodsandtools.com%2farchive%2farchive.php%3fid%3d72" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Acceptance_TDD_Explained</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Acceptance_TDD_Explained</guid>
      <pubDate>Mon, 18 Aug 2008 11:59:42 GMT</pubDate>
    </item>
    <item>
      <title>What's an Auto Mocking Container?</title>
      <description>...it's a really neat tool if you're writing a lot of unit tests and find yourself forever constructing mock objects &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fmikehadlow.blogspot.com%2f2008%2f08%2fwhat-auto-mocking-container.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fmikehadlow.blogspot.com%2f2008%2f08%2fwhat-auto-mocking-container.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/What_s_an_Auto_Mocking_Container</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/What_s_an_Auto_Mocking_Container</guid>
      <pubDate>Wed, 13 Aug 2008 16:52:50 GMT</pubDate>
    </item>
    <item>
      <title>TDD / BDD Example</title>
      <description>&amp;quot;How-to&amp;quot; example of TDD / BDD &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcode.mattcalla.com%2f2008%2f08%2f05%2ftdd--bdd-example.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcode.mattcalla.com%2f2008%2f08%2f05%2ftdd--bdd-example.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/TDD_BDD_Example</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/TDD_BDD_Example</guid>
      <pubDate>Tue, 05 Aug 2008 07:14:13 GMT</pubDate>
    </item>
    <item>
      <title>Phil Haack: Unit Test Boundaries </title>
      <description>One principle to follow when writing a unit test is that a unit test should ideally not cross boundaries. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fhaacked.com%2farchive%2f2008%2f07%2f22%2funit-test-boundaries.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fhaacked.com%2farchive%2f2008%2f07%2f22%2funit-test-boundaries.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Phil_Haack_Unit_Test_Boundaries</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Phil_Haack_Unit_Test_Boundaries</guid>
      <pubDate>Thu, 24 Jul 2008 15:31:09 GMT</pubDate>
    </item>
    <item>
      <title>Getting Started with TDD</title>
      <description>Getting started with Test Driven Development can be challenging.  In this blog post, Steve offers some advice on how to get started either for a brand new project or one that already in maintenance mode. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fstevesmithblog.com%2fblog%2fgetting-started-with-tdd%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fstevesmithblog.com%2fblog%2fgetting-started-with-tdd%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/patterns/Getting_Started_with_TDD</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/patterns/Getting_Started_with_TDD</guid>
      <pubDate>Sun, 20 Jul 2008 15:31:02 GMT</pubDate>
    </item>
    <item>
      <title>TDD, Architecture and Testing Code in Isolation :: Part 3</title>
      <description>Ok, ok, ok, the other two parts where lean on the unit tests.  Now we get down to the mocking, faking, and testing.  The first two tests I wrote have to do with the UserListing Entity.  Once again, since we're in a situation were thing are generated by LINQ, I'm not really sure of a solid reason, or how, to write tests that fail first.  How would one do that for testing entities?  I'm not sure but here are my first two that run returning green lights. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fadronbhall.com%2fblogs%2ftechnology__software_development%2farchive%2f2008%2f07%2f10%2f7409.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fadronbhall.com%2fblogs%2ftechnology__software_development%2farchive%2f2008%2f07%2f10%2f7409.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/TDD_Architecture_and_Testing_Code_in_Isolation_Part_3</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/TDD_Architecture_and_Testing_Code_in_Isolation_Part_3</guid>
      <pubDate>Thu, 10 Jul 2008 16:26:44 GMT</pubDate>
    </item>
    <item>
      <title>TDD, Architecture and Testing Code in Isolation :: Part 2</title>
      <description>In the next part of this series I undertook are some of my various clean ups.  Create respective test classes for each of the pieces of the database that will have respective entities, methods, or objects to test.  But before really getting on a roll with the tests I have to detour through creating a fake for the DataContext Object for my LINQ to SQL Data Access Layer.

So check it out, and send some feedback. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fadronbhall.com%2fblogs%2ftechnology__software_development%2farchive%2f2008%2f07%2f07%2f7390.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fadronbhall.com%2fblogs%2ftechnology__software_development%2farchive%2f2008%2f07%2f07%2f7390.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/TDD_Architecture_and_Testing_Code_in_Isolation_Part_2</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/TDD_Architecture_and_Testing_Code_in_Isolation_Part_2</guid>
      <pubDate>Tue, 08 Jul 2008 04:20:15 GMT</pubDate>
    </item>
    <item>
      <title>TDD and Hard To Test Areas</title>
      <description>I wanted to talk about the issues that people get when they begin working with TDD, the same issues that tend to make them abandon TDD after an initial experiment. Those are the 'hard-to-test' areas, the things production code needs to do, that those presentations and introductory books just don't seem to explain well. In this post we will start with a quick review of TDD, and then get into why people fail when they start trying to use it. Next time around we will look more closely at solutions. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcodebetter.com%2fblogs%2fian_cooper%2farchive%2f2008%2f07%2f07%2ftdd-and-hard-to-test-areas-part1.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcodebetter.com%2fblogs%2fian_cooper%2farchive%2f2008%2f07%2f07%2ftdd-and-hard-to-test-areas-part1.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/TDD_and_Hard_To_Test_Areas</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/TDD_and_Hard_To_Test_Areas</guid>
      <pubDate>Mon, 07 Jul 2008 16:43:41 GMT</pubDate>
    </item>
    <item>
      <title>TDD, Architecture and Testing Code in Isolation :: Part 1</title>
      <description>Just a few examples here.  First we'll setup the basic architecture from the lowest common denominator - the database - bounce up to the first layer, and test in isolation and test in integration.  These examples are simply the easiest ways to test the basic data and data access layer using Stubs, Mocks, and general unit test practices.

irst off here are the pieces of the architecture that you'll NEED regardless.  No real coding in this entry (except for the T-SQL), just setting up the solution to put the tests in and have the initial database architecture setup.  The part 2 entry will have more on the testing, and part 3 will have actual functional code tests and implementations - after all, I'm working this up in a test driven development mentality - &amp;quot;mostly&amp;quot;. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fadronbhall.com%2fblogs%2ftechnology__software_development%2farchive%2f2008%2f07%2f06%2f7366.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fadronbhall.com%2fblogs%2ftechnology__software_development%2farchive%2f2008%2f07%2f06%2f7366.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/TDD_Architecture_and_Testing_Code_in_Isolation_Part_1</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/TDD_Architecture_and_Testing_Code_in_Isolation_Part_1</guid>
      <pubDate>Mon, 07 Jul 2008 05:59:10 GMT</pubDate>
    </item>
    <item>
      <title>Mocking the Linq To Sql DataContext</title>
      <description>A generic solution to mocking the Linq To Sql DataContext and how you can test your linq queries against an in memory database. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fandrewtokeley.net%2farchive%2f2008%2f07%2f06%2fmocking-linq-to-sql-datacontext.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fandrewtokeley.net%2farchive%2f2008%2f07%2f06%2fmocking-linq-to-sql-datacontext.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Mocking_the_Linq_To_Sql_DataContext</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Mocking_the_Linq_To_Sql_DataContext</guid>
      <pubDate>Wed, 09 Jul 2008 00:31:02 GMT</pubDate>
    </item>
    <item>
      <title>The marvelous world of unit testing</title>
      <description>Some rumination on the argument &amp;quot;Unit Testing&amp;quot; &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.nablasoft.com%2falkampfer%2findex.php%2f2008%2f07%2f01%2fthe-wonderful-world-of-unit-testing%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.nablasoft.com%2falkampfer%2findex.php%2f2008%2f07%2f01%2fthe-wonderful-world-of-unit-testing%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/The_marvelous_world_of_unit_testing</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/The_marvelous_world_of_unit_testing</guid>
      <pubDate>Tue, 01 Jul 2008 12:46:09 GMT</pubDate>
    </item>
    <item>
      <title>ASP.NET Design Patterns, TDD and Agile Book List</title>
      <description>I've been collecting book recommendations on software design principles and patterns, test-driven development, and agile development. I wanted to share my current reading list with you in case you are interested in learning more about these topics. If you have any additional book recommendations -- please share!  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdotnet.dzone.com%2fnews%2faspnet-mvc-book-list"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdotnet.dzone.com%2fnews%2faspnet-mvc-book-list" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/aspnet/ASP_NET_Design_Patterns_TDD_and_Agile_Book_List</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/aspnet/ASP_NET_Design_Patterns_TDD_and_Agile_Book_List</guid>
      <pubDate>Mon, 30 Jun 2008 14:27:31 GMT</pubDate>
    </item>
    <item>
      <title>SubSonic: Writing Decoupled, Testable Code With SubSonic 2.1</title>
      <description>I've heard/read rumblings over the last few months that &amp;quot;SubSonic is tightly coupled&amp;quot; and therefore you have to &amp;quot;drag it around&amp;quot; with you in your project. I can see why people might think this - ActiveRecord is not the most testable thing in the world :). I've really tried to push SubSonic into the TDD realm and thought it might be a good idea to show how you can structure up a highly testable, decoupled application using SubSonic as your Data Access tool. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.wekeroad.com%2fblog%2fsubsonic-writing-decoupled-testable-code-with-subsonic-2-1%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.wekeroad.com%2fblog%2fsubsonic-writing-decoupled-testable-code-with-subsonic-2-1%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/SubSonic_Writing_Decoupled_Testable_Code_With_SubSonic_2_1</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/SubSonic_Writing_Decoupled_Testable_Code_With_SubSonic_2_1</guid>
      <pubDate>Wed, 18 Jun 2008 21:31:56 GMT</pubDate>
    </item>
    <item>
      <title>Top 100 Best Software Engineering Books, Ever</title>
      <description>In this post I proudly present the Top 100 of Best Software Engineering Books, Ever. I have created this list using four different criteria: 1) number of Amazon reviews, 2) average Amazon rating, 3) number of Google hits and 4) Jolt awards.
 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.noop.nl%2f2008%2f06%2ftop-100-best-software-engineering-books-ever.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.noop.nl%2f2008%2f06%2ftop-100-best-software-engineering-books-ever.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Top_100_Best_Software_Engineering_Books_Ever</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Top_100_Best_Software_Engineering_Books_Ever</guid>
      <pubDate>Fri, 20 Jun 2008 13:16:02 GMT</pubDate>
    </item>
    <item>
      <title>MVC Storefront, Part 12: Mocking</title>
      <description>In this episode I implement mocking so I can test my Authentication action for my UserController. In order to do this, however, I have to mock up the HttpContext...
Not much else to say here - it's all about Mocking! &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.wekeroad.com%2fmvc-storefront%2fmvcstore-part-12%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.wekeroad.com%2fmvc-storefront%2fmvcstore-part-12%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/aspnet/MVC_Storefront_Part_12_Mocking</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/aspnet/MVC_Storefront_Part_12_Mocking</guid>
      <pubDate>Tue, 27 May 2008 01:16:04 GMT</pubDate>
    </item>
    <item>
      <title>Design for testability - Microsoft Unity (part 7)</title>
      <description>Design for testability - Microsoft Unity &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.vuscode.com%2fmalovicn%2farchive%2f2008%2f05%2f18%2fdesign-for-testability-microsoft-unity-part-7.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.vuscode.com%2fmalovicn%2farchive%2f2008%2f05%2f18%2fdesign-for-testability-microsoft-unity-part-7.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Design_for_testability_Microsoft_Unity_part_7</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Design_for_testability_Microsoft_Unity_part_7</guid>
      <pubDate>Thu, 22 May 2008 10:33:32 GMT</pubDate>
    </item>
    <item>
      <title>The Easy Way to TDD</title>
      <description>Learn how easy TDD can be...  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fstevenharman.net%2fblog%2farchive%2f2008%2f05%2f14%2fthe-easy-way-to-tdd.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fstevenharman.net%2fblog%2farchive%2f2008%2f05%2f14%2fthe-easy-way-to-tdd.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/The_Easy_Way_to_TDD</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/The_Easy_Way_to_TDD</guid>
      <pubDate>Thu, 15 May 2008 17:46:03 GMT</pubDate>
    </item>
    <item>
      <title>The Importance of Unit Testing WCF Attributes</title>
      <description>What happens when you don't test certain WCF Attribute values in your unit tests? Sometimes nothing  - and sometimes all hell breaks loose. I'm scared of the latter. :) 

This is a quick and easy intro into how to unit test your operation contract attribute values.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.donnfelker.com%2f2008%2f05%2f07%2fTheImportanceOfUnitTestingWCFAttributes.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.donnfelker.com%2f2008%2f05%2f07%2fTheImportanceOfUnitTestingWCFAttributes.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/webservices/The_Importance_of_Unit_Testing_WCF_Attributes</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/webservices/The_Importance_of_Unit_Testing_WCF_Attributes</guid>
      <pubDate>Wed, 07 May 2008 18:26:35 GMT</pubDate>
    </item>
    <item>
      <title>unit testing your events</title>
      <description>In this article I will show you how you can unit test your events. I will show you a simple technique that will enable you to test if your events fire exactly as often as you want them to and I will provide you with two implementations. One implementation works well with the .NET Framework 2.0 and the second one uses .NET 3.0 (anonymous methods) in order to minimize the code necessary. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.dotnettoad.com%2findex.php%3f%2farchives%2f12-unit-testing-events.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.dotnettoad.com%2findex.php%3f%2farchives%2f12-unit-testing-events.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/unit_testing_your_events</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/unit_testing_your_events</guid>
      <pubDate>Sun, 04 May 2008 11:01:02 GMT</pubDate>
    </item>
  </channel>
</rss>