Visual Studio 2012 RC – What’s new in Code Coverage

re: Visual Studio 2012 RC – What’s new in Code Coverage

Allen Mathias — Fri, 21 Dec 2012 05:00:30 GMT

Thanks for your feedback @ekleeman.

The exclude attribute continues to work. So if it isn't working for you please get back to us or raise a connect issue and we will definitely investigate why.

For shared projects the use of a .runsettings file is pretty simple and from the feedback received is way better than the .testsettings file experience where you had to maintain a list of your "interested" dlls, keep it updated and have a whole different instrumented build.

re: Visual Studio 2012 RC – What’s new in Code Coverage

ekleeman — Thu, 20 Dec 2012 19:03:59 GMT

This blows.

What you did was make it harder to instrument specific assemblies for solutions that share projects. And the exclude attribute no longer works. So, now we have to create yet another file, .runsettings just to specify instrumentation for each solution. Thanx

re: Visual Studio 2012 RC – What’s new in Code Coverage

Allen Mathias — Tue, 13 Nov 2012 05:41:30 GMT

@Krzysztof yes code coverage for x86 and x64 is supported with the native unit tests in Visual Studio 2012.

You can continue to use AnyCpu for your managed unit test projects and use the new execution engine ie. vstest.console.exe for command line execution.

re: Visual Studio 2012 RC – What’s new in Code Coverage

Krzysztof — Mon, 12 Nov 2012 16:02:15 GMT

Hallo, nice update. I have one question to point '3 Native is a first class citizen' is there support for native x86 or x64 ? Is any cpu supported by MSTest and Coverage test ?

re: Visual Studio 2012 RC – What’s new in Code Coverage

André Krijnen — Tue, 09 Oct 2012 08:18:45 GMT

Thanks it helped me out to configure it well!

re: Visual Studio 2012 RC – What’s new in Code Coverage

Allen Mathias — Thu, 21 Jun 2012 05:18:58 GMT

@Joe

Yes, SharePoint targetted Unit Tests are supported for code coverage.

re: Visual Studio 2012 RC – What’s new in Code Coverage

Allen Mathias — Thu, 21 Jun 2012 05:11:59 GMT

@Tobias

I tried this out on the RC build and I am able to see the correct coverage data and associated coloring.

Would it be possible to share out the testmethod. You can email the same to me @ allendm-msft at hotmail dot com

re: Visual Studio 2012 RC – What’s new in Code Coverage

Joe — Thu, 21 Jun 2012 03:28:08 GMT

Hi Allen,

Do you now support code coverage for SharePoint 2010 (e.g., .NET 3.5 x64 DLLs)? It's possible in VS2010 via VSPerf/VSInstr, but it'd be great if this works "out of box" now (as opposed to just via command line) in VS 2012.

Thanks,

Joe

re: Visual Studio 2012 RC – What’s new in Code Coverage

Tobias Burger — Wed, 20 Jun 2012 12:33:50 GMT

If I test async code and run a Code Coverage Analysis in VS 2012 RC i get the async blocks not covered.

The lines where I call await are colored in yellow and in the Code Coverage Results pane the method that doesn't get covered is "MoveNext()"

[TestMethod]

publis async Task TestAsyncCode()

{

var response = await <asyncmethodtotest>;

Assert...

}

re: Visual Studio 2012 RC – What’s new in Code Coverage

Allen Mathias — Wed, 20 Jun 2012 04:51:34 GMT

@Dimitry no such planned series. The primary objective with both the posts was to give a quick intro to the new features in our areas and therefore I decided to keep the subject similar to Mathew's post on unit testing :)