<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by schefdev</title>
    <description>Stories kicked by schefdev</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>When TDD goes bad</title>
      <description>Last week, at the London .NET User Group meeting, Ian Cooper talked about Test-driven development, focusing on both good and bad practices. I'm a big fan of learning from anti-patterns and mistakes of other people, so the second part of his session was very interesting to me. Here is a short list of things that Ian identified as symptoms that TDD has gone bad in a project, along with my comments... &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fgojko.net%2f2008%2f02%2f25%2fwhen-tdd-goes-bad%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fgojko.net%2f2008%2f02%2f25%2fwhen-tdd-goes-bad%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/When_TDD_goes_bad</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/When_TDD_goes_bad</guid>
      <pubDate>Tue, 26 Feb 2008 03:46:03 GMT</pubDate>
    </item>
  </channel>
</rss>