TestResult upload with mstest does not update code coverage in TFS build reports

TestResult upload with mstest does not update code coverage in TFS build reports by LukasGr

Closed

as Not Reproducible Help for as Not Reproducible

Type:	Bug
ID:	777477
Opened:	1/25/2013 1:46:05 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

We have installed TFS2012 (currently as test environment) as upgrade from TFS2010.
We are running unit tests with mstest. They are published to TFS with mstest, too.
In TFS2010 the calculated code coverage is shown.
In TFS2012 the code coverage column (report "Build Summary") is empty. But code coverage is calculated also from the new build server. (.coverage file is existing and has correct values if I open it in VS.) Also build done before migration still shows code coverage in report.
More details (screenshots, etc.) can be send on request.

Details (expand)

Team Foundation Server 2012

"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\\mstest.exe" /nologo /usestderr /detail:errormessage /testmetadata:"C:\Builds\15\MES\Complete\src\MES_3_X_10.vsmdi" /testsettings:"C:\Builds\15\MES\Complete\src\Local.testsettings" /testlist:ContextFree /resultsfileroot:"C:\Builds\15\MES\Complete\src\TestResults" /publish:http://vm0784:8080/tfs/e5 /teamproject:MES /publishbuild:Complete_20130124.2 "/platform:Any CPU" /flavor:Debug
Loading C:\Builds\15\MES\Complete\src\Local.testsettings...
Loading C:\Builds\15\MES\Complete\src\MES_3_X_10.vsmdi...
Starting execution...

Results             Top Level Tests
-------             ---------------
[...]
108/108 test(s) Passed

Summary
-------
Test Run Warning.
    Passed 108
    -----------
    Total 108
Results file: C:\Builds\15\MES\Complete\src\TestResults\S_TFSBuilder_VM0810 2013-01-24 17_38_56_Any CPU_Debug.trx
Test Settings: Local

Run has the following issue(s):
EXEC : warning : conflict during test run deployment: deployment item 'c:\builds\15\mes\complete\src\test\reporting\core.unittests\bin\debug\Moq.dll' directly or indirectly referenced by the test container 'c:\builds\15\mes\complete\src\test\reporting\core.unittests\bin\debug\ais.mes.reporting.core.unittests.dll' cannot be deployed to 'Moq.dll' because otherwise the file 'c:\builds\15\mes\complete\src\test\reporting\core.unittests\bin\debug\Moq.dll' would overwrite deployment item 'c:\builds\15\mes\complete\src\test\eventmanagement.actions.unittest\bin\debug\Moq.dll' directly or indirectly referenced by the test container 'c:\builds\15\mes\complete\src\test\eventmanagement.actions.unittest\bin\debug\ais.mes.eventmanagement.actions.unittest.dll'. [C:\Builds\15\MES\Complete\BuildType\TFSBuild.proj]
EXEC : warning : Test Run deployment issue: The assembly or module 'System.Windows.Interactivity' directly or indirectly referenced by the test container 'c:\builds\15\mes\complete\src\test\core\bin\debug\ais.mes.core.unittest.dll' was not found. [C:\Builds\15\MES\Complete\BuildType\TFSBuild.proj]
Waiting to publish...
Publishing results of test run S_TFSBuilder@VM0810 2013-01-24 17:38:56_Any CPU_Debug to http://vm0784:8080/tfs/e5...
........Publish completed successfully.

English

Windows Server 2008 R2 SP1

English

No code coverage in (all) build reports.

Code coverage in (all) build reports.

File Name	Submitted By	Submitted On	File Size
BuildQualityIndicators.png (restricted)	LukasGr	2/1/2013	-
BuildSummary.png (restricted)	LukasGr	2/1/2013	-
data.coverage.zip (restricted)	LukasGr	2/1/2013	-

Posted by Microsoft on 5/16/2013 at 11:39 PM

LukasGr,
The issue has been addressed in Update 2 - Please upgrade to TFS 2012.2 and revert if you still see issues.

Thanks,
Visual Studio Product Team

Posted by Microsoft on 2/17/2013 at 6:26 PM

Hi LukasGr, thanks a lot for your response. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.

Posted by LukasGr on 2/15/2013 at 1:25 AM

I've set it to active, now. Hope to get your feedback soon.

Posted by LukasGr on 2/1/2013 at 2:27 AM

Why do you close the issue due to "out of date"? There were not even two days since your request of screenshots!!
I've uploaded now two screenshots from build reports and the code coverage file.

Posted by Microsoft on 1/31/2013 at 1:04 AM

Hi LukasGr, we'll close this feedback because it has been out of date. Please recreate a new feedback if you have not resolved this issue. Thanks.

Posted by Microsoft on 1/29/2013 at 10:27 PM

Hi LukasGr, thank you for submitting feedback on Visual Studio and .Net Framework. Please upload a screenshot or other information. Thanks.

Posted by Microsoft on 1/25/2013 at 1:49 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)