<?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"
	>
<channel>
	<title>Comments on: Short-circuiting code coverage</title>
	<atom:link href="http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/feed/" rel="self" type="application/rss+xml" />
	<link>http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/</link>
	<description>Can you dig it man?</description>
	<pubDate>Sat, 22 Nov 2008 05:53:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Testing the Tests via Mutation &#187; Graphsy Blog &#187; Graph drawing for the web</title>
		<link>http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/#comment-94022</link>
		<dc:creator>Testing the Tests via Mutation &#187; Graphsy Blog &#187; Graph drawing for the web</dc:creator>
		<pubDate>Wed, 29 Oct 2008 22:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/#comment-94022</guid>
		<description>[...] set the ground for this post I first need to reiterate a message that has been heard from many other sources.  Code coverage can only tell you how bad your test suite is, not how good it [...]</description>
		<content:encoded><![CDATA[<p>[...] set the ground for this post I first need to reiterate a message that has been heard from many other sources.  Code coverage can only tell you how bad your test suite is, not how good it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Disco Blog &#187; Blog Archive &#187; Solving the code coverage dilemma with Emma</title>
		<link>http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/#comment-9639</link>
		<dc:creator>The Disco Blog &#187; Blog Archive &#187; Solving the code coverage dilemma with Emma</dc:creator>
		<pubDate>Wed, 25 Apr 2007 01:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/#comment-9639</guid>
		<description>[...] Solving the code coverage dilemma with Emma  Because it&#8217;s my bag, I pointed out recently that copasetic coverage tools (like Cobertura) can inadvertently hide defects by reporting specific lines of code as covered. But, while I often use Cobertura in my examples, I have found that Emma is fairly smart in its reporting of code coverage values. As such, I often find myself running both hip tools for projects. [...]</description>
		<content:encoded><![CDATA[<p>[...] Solving the code coverage dilemma with Emma  Because it&#8217;s my bag, I pointed out recently that copasetic coverage tools (like Cobertura) can inadvertently hide defects by reporting specific lines of code as covered. But, while I often use Cobertura in my examples, I have found that Emma is fairly smart in its reporting of code coverage values. As such, I often find myself running both hip tools for projects. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Test Early &#187; Uncovering code coverage</title>
		<link>http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/#comment-9553</link>
		<dc:creator>Test Early &#187; Uncovering code coverage</dc:creator>
		<pubDate>Mon, 23 Apr 2007 01:05:29 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/04/21/short-circuiting-code-coverage/#comment-9553</guid>
		<description>[...] It turns out that code conditionals are a bit tricky when it comes to measuring code coverage and in certain scenarios, tests can trigger high line and branch coverage rates but fail to uncover nefarious defects. In fact, I recently posted a code example that demonstrates short-circuiting code coverage via a simple OR condition . [...]</description>
		<content:encoded><![CDATA[<p>[...] It turns out that code conditionals are a bit tricky when it comes to measuring code coverage and in certain scenarios, tests can trigger high line and branch coverage rates but fail to uncover nefarious defects. In fact, I recently posted a code example that demonstrates short-circuiting code coverage via a simple OR condition . [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
