<?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: The Code Coverage Metric is Inversely Proportional to the Criticality of the Information It Provides.</title>
	<atom:link href="http://www.testingmentor.com/imtesty/2009/11/13/the-code-coverage-metric-is-inversely-proportional-to-the-criticality-of-the-information-it-provides/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testingmentor.com/imtesty/2009/11/13/the-code-coverage-metric-is-inversely-proportional-to-the-criticality-of-the-information-it-provides/</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: I.M. Testy &#8250; Code Coverage: More Than Just a Number</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/13/the-code-coverage-metric-is-inversely-proportional-to-the-criticality-of-the-information-it-provides/comment-page-1/#comment-588</link>
		<dc:creator>I.M. Testy &#8250; Code Coverage: More Than Just a Number</dc:creator>
		<pubDate>Fri, 22 Jan 2010 02:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/13/the-code-coverage-metric-is-inversely-proportional-to-the-criticality-of-the-information-it-provides/#comment-588</guid>
		<description>[...] of code coverage implies something is well tested. Interestingly enough, 2 years ago I wrote a post illustrating how the metric can be gamed and how the code coverage measure tells us nothing about [...]</description>
		<content:encoded><![CDATA[<p>[...] of code coverage implies something is well tested. Interestingly enough, 2 years ago I wrote a post illustrating how the metric can be gamed and how the code coverage measure tells us nothing about [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I.M. Testy &#8250; Reconsidering Code Coverage</title>
		<link>http://www.testingmentor.com/imtesty/2009/11/13/the-code-coverage-metric-is-inversely-proportional-to-the-criticality-of-the-information-it-provides/comment-page-1/#comment-316</link>
		<dc:creator>I.M. Testy &#8250; Reconsidering Code Coverage</dc:creator>
		<pubDate>Wed, 25 Nov 2009 18:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://testingmentor.com/imtesty/2009/11/13/the-code-coverage-metric-is-inversely-proportional-to-the-criticality-of-the-information-it-provides/#comment-316</guid>
		<description>[...] that testers should not believe high code coverage numbers mean “well tested.” (Again see my blog post from Aug 2007.) Unfortunately, the path to the point was fraught with inaccuracies and tangents that I almost [...]</description>
		<content:encoded><![CDATA[<p>[...] that testers should not believe high code coverage numbers mean “well tested.” (Again see my blog post from Aug 2007.) Unfortunately, the path to the point was fraught with inaccuracies and tangents that I almost [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
