{"id":9091,"date":"2007-07-03T15:12:29","date_gmt":"2007-07-03T15:12:29","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2007\/07\/03\/cool-tool-for-requirements-test-coverage\/"},"modified":"2018-08-14T00:33:18","modified_gmt":"2018-08-14T00:33:18","slug":"cool-tool-for-requirements-test-coverage","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/cool-tool-for-requirements-test-coverage\/","title":{"rendered":"Cool tool for requirements test coverage"},"content":{"rendered":"<p>A few days ago someone forwarded me some links to a tool for determining test coverage (code coverage) on requirements rather than assemblies, classes and methods (which VSTS provides out of the box).&nbsp; I finally got a chance to look over it today.&nbsp; It looks pretty cool.&nbsp; I have to admit I&#8217;m a bit skeptical about annotating every class\/method with the requirement number but that might work out.&nbsp; It would be very interesting to try it out on a project.&nbsp; There&#8217;s no question reporting the test coverage by requirement\/scenario is way more meaningful to managers, project sponsors and users than reporting it on assemblies.\nCheck it out and let me know what you think&#8230;\n<a href=\"http:\/\/www.paulstovell.net\/blog\/index.php\/scenario-coverage-analyser-for-tfs\/\">http:\/\/www.paulstovell.net\/blog\/index.php\/scenario-coverage-analyser-for-tfs\/<\/a><br \/><a href=\"http:\/\/www.paulstovell.net\/blog\/index.php\/scenario-coverage-analyser-for-tfs-setting-it-up\/\">http:\/\/www.paulstovell.net\/blog\/index.php\/scenario-coverage-analyser-for-tfs-setting-it-up\/<\/a>\nThanks Paul for building this,<\/p>\n<p>Brian<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A few days ago someone forwarded me some links to a tool for determining test coverage (code coverage) on requirements rather than assemblies, classes and methods (which VSTS provides out of the box).&nbsp; I finally got a chance to look over it today.&nbsp; It looks pretty cool.&nbsp; I have to admit I&#8217;m a bit skeptical [&hellip;]<\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[5],"class_list":["post-9091","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-tfs"],"acf":[],"blog_post_summary":"<p>A few days ago someone forwarded me some links to a tool for determining test coverage (code coverage) on requirements rather than assemblies, classes and methods (which VSTS provides out of the box).&nbsp; I finally got a chance to look over it today.&nbsp; It looks pretty cool.&nbsp; I have to admit I&#8217;m a bit skeptical [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/9091","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=9091"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/9091\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=9091"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=9091"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=9091"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}