<?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"
	>
<channel>
	<title>Comments on: Are Too Many Mocks A Code Smell?</title>
	<atom:link href="http://blog.james-carr.org/2006/08/14/are-too-many-mocks-a-code-smell/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.james-carr.org/2006/08/14/are-too-many-mocks-a-code-smell/</link>
	<description>Rants and Musings of an Agile Developer</description>
	<pubDate>Sat, 22 Nov 2008 06:43:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Andres Almiray</title>
		<link>http://blog.james-carr.org/2006/08/14/are-too-many-mocks-a-code-smell/#comment-97</link>
		<dc:creator>Andres Almiray</dc:creator>
		<pubDate>Tue, 15 Aug 2006 13:05:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.james-carr.org/?p=34#comment-97</guid>
		<description>I agree. Having many mocks for your test code doesn't mean it is easier to test it in isolation, it means you are doing too much with that class, and that it could be refactored in smaller parts.</description>
		<content:encoded><![CDATA[<p>I agree. Having many mocks for your test code doesn&#8217;t mean it is easier to test it in isolation, it means you are doing too much with that class, and that it could be refactored in smaller parts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
