<?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: Reconsidering Code Coverage</title>
	<atom:link href="http://www.testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/</link>
	<description>Treatises on the practice of software testing</description>
	<lastBuildDate>Sat, 03 Jul 2010 11:49:32 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: OpenQuality.ru &#124; Ноябрьская лента: лучшее за месяц</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/comment-page-1/#comment-322</link>
		<dc:creator>OpenQuality.ru &#124; Ноябрьская лента: лучшее за месяц</dc:creator>
		<pubDate>Mon, 30 Nov 2009 20:15:23 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/#comment-322</guid>
		<description>[...] о тестовом покрытии кода: штука архиполезная, но не серебряная пуля. Подробное рассмотрение на [...]</description>
		<content:encoded><![CDATA[<p>[...] о тестовом покрытии кода: штука архиполезная, но не серебряная пуля. Подробное рассмотрение на [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #486</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/comment-page-1/#comment-318</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #486</dc:creator>
		<pubDate>Fri, 27 Nov 2009 08:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/#comment-318</guid>
		<description>[...] Reconsidering Code Coverage - Bj Rollison discusses the issue of Code Coverage in testing, looking at the various metrics, and discussing the usual question of is high test coverage a good measure of the depth of testing [...]</description>
		<content:encoded><![CDATA[<p>[...] Reconsidering Code Coverage &#8211; Bj Rollison discusses the issue of Code Coverage in testing, looking at the various metrics, and discussing the usual question of is high test coverage a good measure of the depth of testing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: testingmentor</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/comment-page-1/#comment-317</link>
		<dc:creator>testingmentor</dc:creator>
		<pubDate>Thu, 26 Nov 2009 00:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/#comment-317</guid>
		<description>Hi Coderzh,

Agree. I think most people get hung up on the number; esp. those who look at software and only see a black box.</description>
		<content:encoded><![CDATA[<p>Hi Coderzh,</p>
<p>Agree. I think most people get hung up on the number; esp. those who look at software and only see a black box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coderzh</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/comment-page-1/#comment-315</link>
		<dc:creator>Coderzh</dc:creator>
		<pubDate>Wed, 25 Nov 2009 12:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/25/reconsidering-code-coverage/#comment-315</guid>
		<description>Very Agree. I never think code coverage is the most important, but I always use it to find which codes I didn&#039;t coverage.</description>
		<content:encoded><![CDATA[<p>Very Agree. I never think code coverage is the most important, but I always use it to find which codes I didn&#8217;t coverage.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
