<?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>Grading On A Curve</title><link>http://blogs.msdn.com/b/micahel/archive/2005/02/16/374413.aspx</link><description>A topic I've been pondering of late is grading test cases. If I have two test cases that appear to do exactly the same thing, how do I decide which one to keep and which one to turn off? If I am wading though a large number of failing or unstable test</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Grading On A Curve</title><link>http://blogs.msdn.com/b/micahel/archive/2005/02/16/374413.aspx#379073</link><pubDate>Wed, 23 Feb 2005 19:16:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:379073</guid><dc:creator>The Braidy Tester</dc:creator><description>It would indeed be great to have an easy way to annotate test cases with this kind of information, and then use that metadata as part of the queries used to decide which test cases are included in a run. Visual Studio Team System, are you listening? &amp;lt;g/&amp;gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=379073" width="1" height="1"&gt;</description></item><item><title>re: Grading On A Curve</title><link>http://blogs.msdn.com/b/micahel/archive/2005/02/16/374413.aspx#379053</link><pubDate>Wed, 23 Feb 2005 18:50:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:379053</guid><dc:creator>Neilson Eney</dc:creator><description>Long time reader, first time commenter...&lt;br&gt;&lt;br&gt;This post reminds me a lot of how I use iTunes.  I have songs that I really like, I have songs that I hate but are useful to keep around for some special occation, and there are other songs that were bad rips that I need to delete, but maybe I want to re-encode them before I delete them.&lt;br&gt;&lt;br&gt;It occured to me as I read this post that wouldn't it be sweet to have a test case management tool that had some of the same features as iTunes, or other music players?  I already rate my test cases by frequency.  Some test cases are BVT's and are run often, if not nightly.  It all comes down to how &amp;quot;deep&amp;quot; I want the tests to go and how much time I have to execute a given test pass.&lt;br&gt;&lt;br&gt;You say you'd like to know which tests to keep and which to turn off?  Well, what about something less binary?  How about a test you want to run during a test cycle and another test that you'll let run, but you might want to flag is as a potential problem child that needs revisiting after the product ships.  Often it's during the middle of a test cycle that I realize old tests that we thought were good at the outset, actually need some redesign.&lt;br&gt;&lt;br&gt;I already put some limited metadata into my test cases such as the frequency that I run them.  Why not go ahead and add additional metadata that includes the type of &amp;quot;grading&amp;quot; information you're discussing here?  The more knowledge I can capture as I think about test cases, the better since I can then go back and use tools to organize that knowledge to help me make my test cases better. &lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=379053" width="1" height="1"&gt;</description></item><item><title>Importance of testers who code.</title><link>http://blogs.msdn.com/b/micahel/archive/2005/02/16/374413.aspx#378736</link><pubDate>Wed, 23 Feb 2005 13:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:378736</guid><dc:creator>notgartner.com: Mitch Denny's Blog</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=378736" width="1" height="1"&gt;</description></item><item><title>re: Grading On A Curve</title><link>http://blogs.msdn.com/b/micahel/archive/2005/02/16/374413.aspx#376554</link><pubDate>Sat, 19 Feb 2005 12:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:376554</guid><dc:creator>Bruce McLeod</dc:creator><description>Micahel,&lt;br&gt;Yet another great post, keep them coming !&lt;br&gt;&lt;br&gt;Your comment about the iceberg principle, really struck a cord with me and I blogged about it briefly here: &lt;a target="_new" href="http://www.teknologika.com/blog/General/Testing/TheIcebergPrinciple.html"&gt;http://www.teknologika.com/blog/General/Testing/TheIcebergPrinciple.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;Regards,&lt;br&gt;&lt;br&gt;Bruce&lt;br&gt;bruce at teknologika dot com&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=376554" width="1" height="1"&gt;</description></item><item><title>New Team System Stuff - 2005-02-17</title><link>http://blogs.msdn.com/b/micahel/archive/2005/02/16/374413.aspx#375910</link><pubDate>Fri, 18 Feb 2005 09:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:375910</guid><dc:creator>Rob Caron's Blog</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=375910" width="1" height="1"&gt;</description></item></channel></rss>