<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to make sense of Code Coverage metrics</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx</link><description>(co-authored with Brad Wilson ) Even since the release of Visual Studio Team System 2005 with easy to use code coverage tools, people inside (and outside) of Microsoft have been talking about what it means. The most common approach we've seen is for a</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Visual Studio Team System 2008 Test Edition with MSDN Premium Subscription</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#9401867</link><pubDate>Fri, 06 Feb 2009 14:56:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9401867</guid><dc:creator>Termékinformációk fejlesztőknek</dc:creator><description>&lt;p&gt;[ Nacsa S&amp;#225;ndor , 2009. febru&amp;#225;r 6.] Ez a Team System v&amp;#225;ltozat a webalkalmaz&amp;#225;sok &amp;#233;s –szolg&amp;#225;ltat&amp;#225;sok tesztel&amp;#233;s&amp;#233;hez&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9401867" width="1" height="1"&gt;</description></item><item><title>Visual Studio Team System 2008 Development Edition with MSDN Premium Subscription</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#9399283</link><pubDate>Thu, 05 Feb 2009 20:44:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9399283</guid><dc:creator>Termékinformációk fejlesztőknek</dc:creator><description>&lt;p&gt;[ Nacsa S&amp;#225;ndor , 2009. janu&amp;#225;r 19. – febru&amp;#225;r 5.] Ez a Team System v&amp;#225;ltozat fejlett eszk&amp;#246;zrendszert k&amp;#237;n&amp;#225;l&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9399283" width="1" height="1"&gt;</description></item><item><title>New and Notable 148</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#9170307</link><pubDate>Wed, 03 Dec 2008 18:09:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9170307</guid><dc:creator>Sam Gentile's Blog</dc:creator><description>&lt;p&gt;Still real tired from my Oklahoma trip , partying with Raymond sure is exhausting-). Agile/Development Tools On my short list for some time now, is to switch from NUnit to the definitely superior MbUnit. My friend Andrew has done some great work with&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9170307" width="1" height="1"&gt;</description></item><item><title>Thoughts on Code Coverage</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#2469645</link><pubDate>Tue, 08 May 2007 01:51:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2469645</guid><dc:creator>Brad Wilson - The .NET Guy</dc:creator><description>&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2469645" width="1" height="1"&gt;</description></item><item><title>New and Notable 148</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#1829344</link><pubDate>Wed, 07 Mar 2007 20:10:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1829344</guid><dc:creator>Sam Gentile</dc:creator><description>&lt;p&gt;Still real tired from my Oklahoma trip , partying with Raymond sure is exhausting-). Agile/Development&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1829344" width="1" height="1"&gt;</description></item><item><title>Code Coverage </title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#1826163</link><pubDate>Wed, 07 Mar 2007 12:06:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1826163</guid><dc:creator>Christian Bøgh Jensen's Blog</dc:creator><description>&lt;p&gt;James Newkirk has an interesting post on code coverage metrics . It's impossible to use a hard code coverage&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1826163" width="1" height="1"&gt;</description></item><item><title>re: How to make sense of Code Coverage metrics</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#1789539</link><pubDate>Fri, 02 Mar 2007 22:27:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1789539</guid><dc:creator>MattYoung</dc:creator><description>&lt;p&gt;Very true, code coverage only revels what is executed, not what is actually verified, &lt;a rel="nofollow" target="_new" href="http://flickr.com/photos/niallkennedy/330227455/"&gt;http://flickr.com/photos/niallkennedy/330227455/&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;What we really want are unit test analysis tools. Tools which analyze unit tests to determine how effective they are at detecting changes to the code under test. Jester is an example, (&lt;a rel="nofollow" target="_new" href="http://jester.sourceforge.net/"&gt;http://jester.sourceforge.net/&lt;/a&gt;), which makes changes to the code under test and then runs the unit tests to determine if the change is detected. &lt;/p&gt;
&lt;p&gt;This area is still fairly green, but certainly has a lot of potential.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1789539" width="1" height="1"&gt;</description></item><item><title>re: How to make sense of Code Coverage metrics</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#1773056</link><pubDate>Wed, 28 Feb 2007 12:04:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1773056</guid><dc:creator>Paulo Morgado</dc:creator><description>&lt;p&gt;That's why I like mock frameworks (&lt;a rel="nofollow" target="_new" href="http://msmvps.com/blogs/paulomorgado/archive/2007/02/17/unit-testing-and-mock-frameworks.aspx"&gt;http://msmvps.com/blogs/paulomorgado/archive/2007/02/17/unit-testing-and-mock-frameworks.aspx&lt;/a&gt;). I can get near 100% code coverage (I want an absolute 100% but Visual Studio says 98% and can't paint any uncovered code). I usually mock my onw internal members to test my public members.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1773056" width="1" height="1"&gt;</description></item><item><title>re: How to make sense of Code Coverage metrics</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#1767307</link><pubDate>Tue, 27 Feb 2007 09:03:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1767307</guid><dc:creator>jrshaw</dc:creator><description>&lt;p&gt;These are good examples of my fundamental rule that metrics must be interpreted within context. &amp;nbsp;You can read more at &lt;a rel="nofollow" target="_new" href="http://blog.panopticode.org/articles/2007/02/26/metrics-must-be-interpreted-in-context"&gt;http://blog.panopticode.org/articles/2007/02/26/metrics-must-be-interpreted-in-context&lt;/a&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1767307" width="1" height="1"&gt;</description></item><item><title>Thoughts on Code Coverage</title><link>http://blogs.msdn.com/b/jamesnewkirk/archive/2007/02/25/how-to-make-sense-of-code-coverage-metrics.aspx#1766286</link><pubDate>Tue, 27 Feb 2007 02:52:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1766286</guid><dc:creator>Espresso Fueled Agile Development</dc:creator><description>&lt;p&gt;Jim Newkirk and Brad Wilson have an interesting blog post on code coverage and what it means . They have&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1766286" width="1" height="1"&gt;</description></item></channel></rss>