<?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: Unit Tests and Code Coverage with PHPT</title>
	<atom:link href="http://matthewturland.com/2008/05/23/unit-tests-and-code-coverage-with-phpt/feed/" rel="self" type="application/rss+xml" />
	<link>http://matthewturland.com/2008/05/23/unit-tests-and-code-coverage-with-phpt/</link>
	<description></description>
	<lastBuildDate>Mon, 08 Mar 2010 16:47:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Glagla Dot Org - Olivier Mansour  &#187; Blogmarks pour le  05/06/2008</title>
		<link>http://matthewturland.com/2008/05/23/unit-tests-and-code-coverage-with-phpt/comment-page-1/#comment-196</link>
		<dc:creator>Glagla Dot Org - Olivier Mansour  &#187; Blogmarks pour le  05/06/2008</dc:creator>
		<pubDate>Thu, 05 Jun 2008 18:37:22 +0000</pubDate>
		<guid isPermaLink="false">tag:ishouldbecoding.com,2008:unit-tests-and-code-coverage-with-phpt/1211553757#comment-196</guid>
		<description>...p&lt;/a&gt; &lt;a href=&quot;http://blogmarks.net/user/kasi77/tag/benchmark&quot;&gt;benchmark&lt;/a&gt;)  &lt;a href=&quot;http://ishouldbecoding.com/2008/05/23/unit-tests-and-code-coverage-with-phpt&quot;&gt;i should be coding :: unit tests and code coverage with phpt&lt;/a&gt;
My initial experiences with unit testing and PHP were with PHPUnit. While it’s a great tool a...</description>
		<content:encoded><![CDATA[<p>&#8230;p <a href="http://blogmarks.net/user/kasi77/tag/benchmark">benchmark</a>)  <a href="http://ishouldbecoding.com/2008/05/23/unit-tests-and-code-coverage-with-phpt">i should be coding :: unit tests and code coverage with phpt</a><br />
My initial experiences with unit testing and PHP were with PHPUnit. While it’s a great tool a&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Turland&#8217;s Blog: Unit Tests and Code Coverage with PHPT &#124; Development Blog With Code Updates : Developercast.com</title>
		<link>http://matthewturland.com/2008/05/23/unit-tests-and-code-coverage-with-phpt/comment-page-1/#comment-193</link>
		<dc:creator>Matthew Turland&#8217;s Blog: Unit Tests and Code Coverage with PHPT &#124; Development Blog With Code Updates : Developercast.com</dc:creator>
		<pubDate>Mon, 26 May 2008 13:06:06 +0000</pubDate>
		<guid isPermaLink="false">tag:ishouldbecoding.com,2008:unit-tests-and-code-coverage-with-phpt/1211553757#comment-193</guid>
		<description>...title=&quot;View all posts in Development&quot; rel=&quot;category tag&quot;&gt;Development&lt;/a&gt;   Matthew Turland has &lt;a href=&quot;http://ishouldbecoding.com/2008/05/23/unit-tests-and-code-coverage-with-phpt&quot;&gt;posted about&lt;/a&gt; some of his experience with &lt;a href=&quot;http://qa.php.net/write-test.php&quot;&gt;PHPT&lt;/a&gt; tests with &lt;a href=&quot;=&quot;&gt;...</description>
		<content:encoded><![CDATA[<p>&#8230;title=&#8221;View all posts in Development&#8221; rel=&#8221;category tag&#8221;>Development   Matthew Turland has <a href="http://ishouldbecoding.com/2008/05/23/unit-tests-and-code-coverage-with-phpt">posted about</a> some of his experience with <a href="http://qa.php.net/write-test.php">PHPT</a> tests with <a href="=">&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis Swicegood</title>
		<link>http://matthewturland.com/2008/05/23/unit-tests-and-code-coverage-with-phpt/comment-page-1/#comment-192</link>
		<dc:creator>Travis Swicegood</dc:creator>
		<pubDate>Sun, 25 May 2008 17:02:38 +0000</pubDate>
		<guid isPermaLink="false">tag:ishouldbecoding.com,2008:unit-tests-and-code-coverage-with-phpt/1211553757#comment-192</guid>
		<description>FYI: I talked with Sebastian about that this week.  The code coverage report generator from PHPUnit is going to be refactored into a separate package so we can share it amongst all of the testing tools.  No timeline on it though...</description>
		<content:encoded><![CDATA[<p>FYI: I talked with Sebastian about that this week.  The code coverage report generator from PHPUnit is going to be refactored into a separate package so we can share it amongst all of the testing tools.  No timeline on it though&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Billyboylindien</title>
		<link>http://matthewturland.com/2008/05/23/unit-tests-and-code-coverage-with-phpt/comment-page-1/#comment-191</link>
		<dc:creator>Billyboylindien</dc:creator>
		<pubDate>Sat, 24 May 2008 16:12:28 +0000</pubDate>
		<guid isPermaLink="false">tag:ishouldbecoding.com,2008:unit-tests-and-code-coverage-with-phpt/1211553757#comment-191</guid>
		<description>Thanks for the tips 
</description>
		<content:encoded><![CDATA[<p>Thanks for the tips</p>
]]></content:encoded>
	</item>
</channel>
</rss>
