<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Developer testing is not primarily about design</title>
	<atom:link href="http://www.moseshohman.com/blog/2007/07/27/developer-testing-is-not-primarily-about-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.moseshohman.com/blog/2007/07/27/developer-testing-is-not-primarily-about-design/</link>
	<description>software development, informatics, etc.</description>
	<lastBuildDate>Tue, 23 Aug 2011 22:57:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Wolfram Arnold</title>
		<link>http://www.moseshohman.com/blog/2007/07/27/developer-testing-is-not-primarily-about-design/comment-page-1/#comment-2387</link>
		<dc:creator>Wolfram Arnold</dc:creator>
		<pubDate>Sat, 14 Feb 2009 00:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.moseshohman.com/blog/2007/07/27/48#comment-2387</guid>
		<description>&lt;p&gt;And there is one more effect I would add:  By adopting a test-first process, you&#039;re frontloading all the questions and uncertainties and miscommunications.  If the developer can&#039;t formulate a concise test, chances are they&#039;re not fully clear about the requirements.  It&#039;s better to flush this out at the beginning when it&#039;s cheap to fix, than implement something that&#039;s off-spec and let QA (if you still have it) or, worst (because most expensive) the customer find it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>And there is one more effect I would add:  By adopting a test-first process, you&#8217;re frontloading all the questions and uncertainties and miscommunications.  If the developer can&#8217;t formulate a concise test, chances are they&#8217;re not fully clear about the requirements.  It&#8217;s better to flush this out at the beginning when it&#8217;s cheap to fix, than implement something that&#8217;s off-spec and let QA (if you still have it) or, worst (because most expensive) the customer find it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Ashley</title>
		<link>http://www.moseshohman.com/blog/2007/07/27/developer-testing-is-not-primarily-about-design/comment-page-1/#comment-2187</link>
		<dc:creator>Steven Ashley</dc:creator>
		<pubDate>Fri, 27 Jul 2007 18:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.moseshohman.com/blog/2007/07/27/48#comment-2187</guid>
		<description>&lt;p&gt;I couldn&#039;t agree more, one more thing, care needs to be taken that the team isn&#039;t &quot;too close&quot; when developing the tests.  Personally, I have found, I can be to close to the code to adequately create tests for it, missing the forest because all the trees kept getting in the way.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more, one more thing, care needs to be taken that the team isn&#8217;t &#8220;too close&#8221; when developing the tests.  Personally, I have found, I can be to close to the code to adequately create tests for it, missing the forest because all the trees kept getting in the way.</p>]]></content:encoded>
	</item>
</channel>
</rss>

