Code coverage gets wrong if multiple test runs will be published for the same build by LukasGr

Resolved

as External Help for as External

Type:	Bug
ID:	773501
Opened:	12/5/2012 1:07:25 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I've a big solution of CSharp projects.
I'm using msbuild script to build the code and to execute tests with mstest.
The tests will be executed with multiple calls of mstest including direct publish to the team foundation server.
In the build report (e.g. "Build Quality Indicators") the code coverage is wrong and not the overall values.

Visual Studio version and Team Foundation Server version are 2010. (I could not select them in the list.)

On Request I can send more detailed information. Please specify required information.

Details (expand)

Team Foundation Server 2012

1. Create Unittests and split them in several Testlists
2. Execute tests and calculate overall code coverage
3. Publish test results (and code coverage) to TFS
4. Check Build report

English

Any

English

In my example I've currently a real code coverage of about 4 percent.
The Build Reports shows about 50 percent.

Code coverage should be equal.

0 attachments

Posted by Microsoft on 12/6/2012 at 12:22 AM

The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx

Posted by Microsoft on 12/5/2012 at 1:50 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)

Microsoft