<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Weaving the test fabric</title>
	<link>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/</link>
	<description>Alex Miller's technical blog</description>
	<pubDate>Thu, 20 Nov 2008 12:59:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Kablooie! &#187; Blog Archive &#187; Should Guice be used in unit tests redux</title>
		<link>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/#comment-49808</link>
		<pubDate>Wed, 21 May 2008 19:58:56 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/#comment-49808</guid>
					<description>[...] One thing I do completely agree with Bob on is that unit tests alone are never enough. Alex Miller wrote a great post about that called Weaving the Test Fabric. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] One thing I do completely agree with Bob on is that unit tests alone are never enough. Alex Miller wrote a great post about that called Weaving the Test Fabric. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alex Miller - Practical unit testing</title>
		<link>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/#comment-28701</link>
		<pubDate>Sat, 23 Feb 2008 04:38:19 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/#comment-28701</guid>
					<description>[...] As Howard mentioned in his blog, there is a lot of value to be had in integration tests as well, and I&amp;#8217;m a big fan of having both unit and integration tests to cover the same code base. Or rather, my favorite is to have unit tests, component level tests, and system level integration tests. These three levels weave together to give you a really powerful safety net for your code. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] As Howard mentioned in his blog, there is a lot of value to be had in integration tests as well, and I&#8217;m a big fan of having both unit and integration tests to cover the same code base. Or rather, my favorite is to have unit tests, component level tests, and system level integration tests. These three levels weave together to give you a really powerful safety net for your code. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anne Botha &#187; KAT - KnowledgeTree Automation Test</title>
		<link>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/#comment-1554</link>
		<pubDate>Thu, 29 Mar 2007 21:26:31 +0000</pubDate>
		<guid>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/#comment-1554</guid>
					<description>[...] http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] <a href='http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/' rel='nofollow'>http://tech.puredanger.com/2007/03/27/weaving-the-test-fabric/</a> [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
