<?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: Clever Design meets TDD</title>
	<atom:link href="http://www.phpaddiction.com/tags/unit-testing/clever-design-meets-tdd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.phpaddiction.com/tags/unit-testing/clever-design-meets-tdd/</link>
	<description></description>
	<lastBuildDate>Thu, 08 Jul 2010 03:46:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Loïc Hoguin</title>
		<link>http://www.phpaddiction.com/tags/unit-testing/clever-design-meets-tdd/comment-page-1/#comment-7510</link>
		<dc:creator>Loïc Hoguin</dc:creator>
		<pubDate>Wed, 05 Mar 2008 02:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpaddiction.com/tags/unit-testing/clever-design-meets-tdd/#comment-7510</guid>
		<description>Keep in mind that you&#039;ll never have 100% code coverage in unit tests, and even if you&#039;re near it won&#039;t prevent bugs that you didn&#039;t think could happen. Sometimes it&#039;s better to just go on and add tests when you stumble on bugs to prevent regression. Another good moment to write tests is when you refactorize a part of your code without changing its interface. You&#039;ll be able to ensure the output looks the same as your previous version of the code, and that&#039;ll add more tests to your project.

Testability is an important part of our framework and despite this we don&#039;t have that much tests yet since we only add tests when we stumble on problems or when refactoring. But then again we&#039;re not proponents of TDD, we just appreciate the usefulness of unit testing.</description>
		<content:encoded><![CDATA[<p>Keep in mind that you'll never have 100% code coverage in unit tests, and even if you're near it won't prevent bugs that you didn't think could happen. Sometimes it's better to just go on and add tests when you stumble on bugs to prevent regression. Another good moment to write tests is when you refactorize a part of your code without changing its interface. You'll be able to ensure the output looks the same as your previous version of the code, and that'll add more tests to your project.</p>
<p>Testability is an important part of our framework and despite this we don't have that much tests yet since we only add tests when we stumble on problems or when refactoring. But then again we're not proponents of TDD, we just appreciate the usefulness of unit testing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
