RichB posted the following comment:

...

Now, if Microsoft were to produce a set of functionality which “profiled”; code and allowed a functional tester to see a straight percentage of how much of the codebase they had exercised during a black-box QA session and linked this with test scripts (English, verbal, scripts) and a bug database - it would be much more useful to most of the QA teams out there. Imagine setting a “profile”; flag in an ASP.Net website and then getting the QA team to test a build of the website. After the QA session ends, the profile gets attached to the test management application for that particular test run. The developer logs onto the test management application to see the results of the test run - and sees graphically which parts of the code got executed, which caused exceptions, which caused crashed and bugs that were entered. If Microsoft can deliver this functionality, then they have hit the holy grail.

--

Rich, thanks again for taking the time to post your comments… I really appreciate your feedback.

The scenario you mention above will be possible in Visual Studio Team System in two ways [YES! We can do this for you!]:

ASP.NET Profiling: As you mention you instrument the code used by the ASP.NET site, point testers or automated test scenarios at the site, and when the cycle is over collect performance data concerning how the ASP.NET application performed.

ASP.NET Code Coverage: Again, as you note above, you instrument the code used by the ASP.NET application, run your functional tests or have testers use the application, and when the cycle is over collect information specifically concerning exactly what code in your ASP.NET application was touched by your test activity.

The great thing is that this functionality, Profiling and Code Coverage, are both offered for all types of tests and all types of applications. Profiling enables developers to see exactly how much time a specific method took to execute along with many other performance related information. Code Coverage gives you percentages and roll ups of what was hit by a test or a scenario and actually can show you visually what code was touched in your application vs. missed. Check out the great article by my partner-in-crime Tom Arnold and Paul Schafer: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvsent/html/vsts-test.asp for an actual screen shot (though the example provided is not ASP.NET specific).

ASP.NET specific functionality was not included in the bits that we made available at Tech Ed... Code Coverage and Profiling work - but not with ASP.NET at this point. This ASP.NET specific functionality will be there for Final Release.