<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>testdrivendevelopment at Yahoo! Groups</title>
    <link>http://groups.yahoo.com/group/testdrivendevelopment/</link>
    <description>Test-driven Development</description>

    <item>
      <title>ANN: NUnitLite 0.9 Release</title>
      <pubDate>Mon, 06 May 2013 18:33:45 GMT</pubDate>
      <dc:creator>Charlie Poole</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35472</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35472</guid>
      <description>Hi All, I&#39;m announcing the release of NUnitLite 0.9 today. In case you were not aware, NUnitLite has surprised me by attracting a lot of users who previously</description>
    </item>
    <item>
      <title>Re: If you could get your colleagues to read just one book on TDD, w</title>
      <pubDate>Mon, 06 May 2013 14:39:57 GMT</pubDate>
      <dc:creator>Al Chou</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35471</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35471</guid>
      <description>I came up with an easy way to generate Mikado diagrams programmatically using Ruby-Graphviz.  One of the co-authors of the book (Ola) liked it.  Here&#39;s an</description>
    </item>
    <item>
      <title>Re: [Summary] If you could get your colleagues to read just one book</title>
      <pubDate>Mon, 06 May 2013 07:26:36 GMT</pubDate>
      <dc:creator>Matteo Vaccari</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35470</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35470</guid>
      <description>... I for one think it&#39;s a very good book on its own merit.  There are other good books on TDD, and GOOS is certainly one of the best, but I think it&#39;s better</description>
    </item>
    <item>
      <title>[Summary] If you could get your colleagues to read just one book on </title>
      <pubDate>Mon, 06 May 2013 02:10:45 GMT</pubDate>
      <dc:creator>John Carter</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35469</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35469</guid>
      <description>Test Driven Development by Example (Kent Beck) + 4 GOOS + 2 Refactoring + 2 Working Effectively With Legacy Code + 2 Clean Code + 1 The Mikado Method</description>
    </item>
    <item>
      <title>Re: If you could get your colleagues to read just one book on TDD, w</title>
      <pubDate>Mon, 06 May 2013 01:34:18 GMT</pubDate>
      <dc:creator>John Carter</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35468</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35468</guid>
      <description>... Now THAT is a Very Good Find! An Excellent Book! Thanks, just what I was hoping for! -- ... This email, including any attachments, is only for the intended</description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Fri, 03 May 2013 20:29:09 GMT</pubDate>
      <dc:creator>Adam Sroka</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35467</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35467</guid>
      <description>It could, but it doesn&#39;t necessarily. The only time I have ever seen it become a problem is when someone was doing something they shouldn&#39;t irrespective of the</description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Fri, 03 May 2013 20:14:29 GMT</pubDate>
      <dc:creator>George Dinwiddie</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35466</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35466</guid>
      <description>Adam, ... Thanks for the admonition. I was just trying to explain how monkey-patching causes more interference between tests than mocks do. - George ... -- ...</description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Fri, 03 May 2013 17:50:34 GMT</pubDate>
      <dc:creator>Adam Sroka</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35465</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35465</guid>
      <description>Perl was my first professional language. I am not afraid of monkey patching. A hammer is a useful tool. Please refrain from hitting yourself with it. ... </description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Fri, 03 May 2013 00:03:02 GMT</pubDate>
      <dc:creator>George Dinwiddie</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35464</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35464</guid>
      <description>Adam, ... No, with monkey patching you&#39;re often messing up *library code* to the detriment of other tests. ... Maybe. Or maybe your monkey patching makes other</description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Thu, 02 May 2013 23:15:36 GMT</pubDate>
      <dc:creator>Adam Sroka</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35463</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35463</guid>
      <description>Hi George: That makes sense, but you can do the same thing to yourself with mocks. That&#39;s why you have to make sure you write microtests for both sides of the </description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Thu, 02 May 2013 14:46:46 GMT</pubDate>
      <dc:creator>George Dinwiddie</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35462</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35462</guid>
      <description>Adam, ... Monkey patching is a common method to create testing seams, even by people who would not use monkey patching in the deliverable system code. It&#39;s a</description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Thu, 02 May 2013 08:57:29 GMT</pubDate>
      <dc:creator>Adrian Howard</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35461</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35461</guid>
      <description>... Well - the same thing kind-of applies in perl. Default initialisation and left over correct values can lead to the wrong behaviour in Perl too. I&#39;m sure</description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Thu, 02 May 2013 03:25:25 GMT</pubDate>
      <dc:creator>Adam Sroka</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35460</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35460</guid>
      <description>Maybe I&#39;m just dense, but: what is it about this that is particular to TDD? Seems to me that monkey patching without tests is *fuck all* more dangerous than</description>
    </item>
    <item>
      <title>Re: What I hate about *Unit frameworks.</title>
      <pubDate>Thu, 02 May 2013 03:12:31 GMT</pubDate>
      <dc:creator>John Roth</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35459</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35459</guid>
      <description>... Snort. This is a continuing issue for the Python developers as well. John Roth [Non-text portions of this message have been removed]</description>
    </item>
    <item>
      <title>Re: If you could get your colleagues to read just one book on TDD, w</title>
      <pubDate>Thu, 02 May 2013 01:03:56 GMT</pubDate>
      <dc:creator>George Dinwiddie</dc:creator>
      <link>http://groups.yahoo.com/group/testdrivendevelopment/message/35458</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/testdrivendevelopment/message/35458</guid>
      <description>Dennis, ... You should pair that with The Mikado Method (mikadomethod.org) - George -- ... * George Dinwiddie *                      http://blog.gdinwiddie.com</description>
    </item>

  </channel>
</rss>
<!-- rss1.grp.bf1.yahoo.com uncompressed Sat May 18 08:46:58 PDT 2013 -->
