<?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>James Whittaker Netcast</title><link>http://blogs.msdn.com/steverowe/archive/2009/01/09/james-whittaker-netcast.aspx</link><description>James Whittaker is the author of books like How To Break Software.&amp;#160; He ran one of the few university-level testing programs at Florida Tech.&amp;#160; He's now as Microsoft and helping Visual Studio become better at testing.&amp;#160; The guys at .Net Rocks</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Dew Drop - January 10, 2009 | Alvin Ashcraft's Morning Dew</title><link>http://blogs.msdn.com/steverowe/archive/2009/01/09/james-whittaker-netcast.aspx#9304717</link><pubDate>Sun, 11 Jan 2009 00:29:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9304717</guid><dc:creator>Dew Drop - January 10, 2009 | Alvin Ashcraft's Morning Dew</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.alvinashcraft.com/2009/01/10/dew-drop-january-10-2009/"&gt;http://www.alvinashcraft.com/2009/01/10/dew-drop-january-10-2009/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: James Whittaker Netcast</title><link>http://blogs.msdn.com/steverowe/archive/2009/01/09/james-whittaker-netcast.aspx#9414009</link><pubDate>Thu, 12 Feb 2009 07:04:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9414009</guid><dc:creator>Yuklai</dc:creator><description>&lt;p&gt;&amp;quot;...if all developers can understand that you can have 100% code coverage and you can still have lots and lots of bug...&amp;quot;&lt;/p&gt;
&lt;p&gt;1. Nobody would use the term &amp;quot;100% code coverage&amp;quot;. It means as much as &amp;quot;100 foos&amp;quot;. When you talk about code coverage and attach a percentage in front of it, you better mention what code coverage criteria you are using. It's hard to imagine such thing as 100% code coverage that's useful, at least not in real product. &lt;/p&gt;
&lt;p&gt;2. Code coverage doesn't mean code quality. Code with higher % code code coverage (any criteria) does not mean better quality.&lt;/p&gt;
</description></item><item><title>re: James Whittaker Netcast</title><link>http://blogs.msdn.com/steverowe/archive/2009/01/09/james-whittaker-netcast.aspx#9414010</link><pubDate>Thu, 12 Feb 2009 07:05:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9414010</guid><dc:creator>Yuklai</dc:creator><description>&lt;p&gt;&amp;quot;...if all developers can understand that you can have 100% code coverage and you can still have lots and lots of bug...&amp;quot;&lt;/p&gt;
&lt;p&gt;1. Nobody would use the term &amp;quot;100% code coverage&amp;quot;. It means as much as &amp;quot;100 foos&amp;quot;. When you talk about code coverage and attach a percentage in front of it, you better mention what code coverage criteria you are using. It's hard to imagine such thing as 100% code coverage that's useful, at least not in real product. &lt;/p&gt;
&lt;p&gt;2. Code coverage doesn't mean code quality. Code with higher % code code coverage (any criteria) does not mean better quality.&lt;/p&gt;
</description></item></channel></rss>