Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
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). I finally got a chance to look over it today. It looks pretty cool. I have to admit I'm a bit skeptical about annotating every class/method with the requirement number but that might work out. It would be very interesting to try it out on a project. There'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.
Check it out and let me know what you think...
Thanks Paul for building this,