<?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: Code Coverage: More Than Just a Number</title>
	<atom:link href="http://www.testingmentor.com/imtesty/2010/01/21/code-coverage-more-than-just-a-number/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testingmentor.com/imtesty/2010/01/21/code-coverage-more-than-just-a-number/</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: Lanette</title>
		<link>http://www.testingmentor.com/imtesty/2010/01/21/code-coverage-more-than-just-a-number/comment-page-1/#comment-661</link>
		<dc:creator>Lanette</dc:creator>
		<pubDate>Mon, 29 Mar 2010 19:04:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.testingmentor.com/imtesty/2010/01/21/code-coverage-more-than-just-a-number/#comment-661</guid>
		<description>I came back to this post again and cracked up when I realized you say here that in 2007 you shouldn&#039;t have been allowed to play with hammers. By that, I mean that you have a post about code coverage telling us nothing about overall quality that you link to. :)

Is it ok if I use a quote from this blog post and link to it? I&#039;m writing something about testing beyond code coverage (so basically, targeting areas unlikely to already be covered). The point is that most advocates of using code coverage tools already understand what it is used for, and I doubt many people are left who are still of the mistaken mindset that 100% code coverage=100% test coverage. I&#039;m not planning to argue for or against that, just to say that the conversation has moved past that, and that I want to talk about testing in the space beyond those basics.

Let me know if the general idea sounds ok and I&#039;ll send you a draft so you know what I&#039;m talking about and can approve or decline.

Thanks,
Lanette

&lt;blockquote&gt;&lt;em&gt; Hi Lanette, 
Yes, you are free to quote anything from my blog posts. 

I agree and I suspect that most folks understand that code coverage != test coverage. But, I also think that many people get hung up on the raw number which is silly. 

As I said in the post in 2007 &quot; the most important measure with regards to code coverage is not how much has been exercised, but the percentage of code that has been unexercised by our testing.&quot;

Part of our job as testers is to investigate the untested areas of untested code. That is what code coverage analysis is. If it is important to reduce our susceptibility to risk in those untested areas of code then we must analyze the untested areas and see if we can design tests to evaluate that code efficiently. </description>
		<content:encoded><![CDATA[<p>I came back to this post again and cracked up when I realized you say here that in 2007 you shouldn&#8217;t have been allowed to play with hammers. By that, I mean that you have a post about code coverage telling us nothing about overall quality that you link to. <img src='http://testingmentor.com/imtesty/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Is it ok if I use a quote from this blog post and link to it? I&#8217;m writing something about testing beyond code coverage (so basically, targeting areas unlikely to already be covered). The point is that most advocates of using code coverage tools already understand what it is used for, and I doubt many people are left who are still of the mistaken mindset that 100% code coverage=100% test coverage. I&#8217;m not planning to argue for or against that, just to say that the conversation has moved past that, and that I want to talk about testing in the space beyond those basics.</p>
<p>Let me know if the general idea sounds ok and I&#8217;ll send you a draft so you know what I&#8217;m talking about and can approve or decline.</p>
<p>Thanks,<br />
Lanette</p>
<blockquote><p><em> Hi Lanette,<br />
Yes, you are free to quote anything from my blog posts. </p>
<p>I agree and I suspect that most folks understand that code coverage != test coverage. But, I also think that many people get hung up on the raw number which is silly. </p>
<p>As I said in the post in 2007 &#8221; the most important measure with regards to code coverage is not how much has been exercised, but the percentage of code that has been unexercised by our testing.&#8221;</p>
<p>Part of our job as testers is to investigate the untested areas of untested code. That is what code coverage analysis is. If it is important to reduce our susceptibility to risk in those untested areas of code then we must analyze the untested areas and see if we can design tests to evaluate that code efficiently.</em></p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>
