blocks|key|3988348|text|将运行设置文件添加到源代码管理。将测试设置为自定义并指向运行设置文件。有关使用.runsettings文件的更多信息，可以在msdn：http://msdn.microsoft.com/en-us/library/jj159530.aspx上找到。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3988349|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/jj159530.aspx^0|1V|1H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Add a run settings file to source control. Set the tests to custom and point to the run settings file. More info on using the .runsettings file can be found on msdn: <a href="http://msdn.microsoft.com/en-us/library/jj159530.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/jj159530.aspx</a>

blocks|key|3988361|text|我也遇到了同样的问题。我的问题是关于ModulePath的。MSDN示例建议您只使用目标二进制文件的名称。这对我不管用。但是，当我将名称作为正则表达式时，它起了作用。我还将生成输出转储到一个文件夹中，以便找到pdb和其他参考文件。希望这能有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3988362|<ModulePath>.*Administration\.dll.*</ModulePath>|code-block|syntax|javascript|3988363|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I was experiencing the same problem. My issue was with the ModulePath. The MSDN examples suggest you can just use the name of a target binary. That was not working for me. However, when I made the name a regular expression, it worked. I am also dumping build output into one folder so that pdb and other reference files are found. Hope that helps.

<pre><code>&lt;ModulePath&gt;.*Administration\.dll.*&lt;/ModulePath&gt;
</code></pre>

blocks|key|4679201|text|我正在使用带有.runsettings文件的本地构建服务器，而且我遇到了完全相同的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4679202|上面的诡计都没有起作用，所以我在托管的构建控制器上测试了构建脚本，它运行得很好，所以我决定问题必须是构建服务器本身。|4679203|我在TFS配置工具中将Build+从"Network“更改为常规windows用户帐户，现在收集代码覆盖率。请注意，此用户将需要访问TFS构建目录。|offset|length|style|BOLD|4679204|entityMap^0|0|0|1|G|U|D|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]|$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

I am using local build server with Visual Studio online with a .runsettings file and I had exactly the same issue.

None of the trickery above helped, so I tested the build script on the hosted build controller and it worked fine, so I decided the problem must be the build server itself.

I changed the Build Service account from "Network Service" to a regular windows user account in the TFS Configuration Tool and now code coverage is collected. Note that this user will need access to the TFS build directories.

blocks|key|4284277|text|我发现这个问题是因为我在这篇文章上看到了一些特别的东西。(查找默认为60的“延迟”设置)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4284278|d.添加一个新的参数‘延迟’，输入下面提到的详细信息-延迟，方向-+In，ArgumentType-+in+32，默认值-+60此参数需要延迟覆盖检查，以便所需的生成详细信息由构建代理填充，此延迟因系统而异，在某些情况下这可能根本不需要。|4284279|http://www.prowareness.com/blog/failing-build-on-insufficient-code-coverageblock-coverage-part-3/|offset|length|4284280|也许尝试在您正在使用的模板中添加一个“延迟”工作流项.|4284281|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|2P|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$F|T|G|U|1|V]]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|E]]]]

I found this question because I saw something peculiar on this article. (Look for the "Delay" setting that defaults to 60). 

d. Add a new argument ‘Delay’, enter details as mentioned below
Name – Delay, Direction – In, ArgumentType-Int32, Default Value – 60
This argument is required to delay coverage check, so that required build details are filled up by the build agent, this delay varies from
system to system, in some cases this might not be required at all. 

<a href="http://www.prowareness.com/blog/failing-build-on-insufficient-code-coverageblock-coverage-part-3/" rel="nofollow">http://www.prowareness.com/blog/failing-build-on-insufficient-code-coverageblock-coverage-part-3/</a>

Maybe try putting in a "delay" work-flow item in the template you are using.......

So our TFS 2013 builds do everything correctly except report code coverage. I've seen similar questions here, e.g. <a href="https://stackoverflow.com/questions/24016217/tfs-2013-no-code-coverage-results">TFS 2013 - No Code Coverage Results</a>, but we've already tried the suggested fixes with no results. 

UPDATE 1 — we've taken more steps to try to resolve this; here's the complete list:

<ul>
<li>Ensured Visual Studio Ultimate was installed on the build server</li>
<li>Tried setting the build definition's "CodeCoverageEnabled" to true as well as the "Code coverage is enabled" setting</li>
<li>Ensured the build was using the Debug configuration and that PDBs were being generated for the DLLs to be tested</li>
<li>Added a .runsettings file with the correct ModulePath included under &lt;CodeCoverage&gt; (verified in build log that the module path was being interpreted correctly; it would produce errors if we intentionally malformed it)</li>
<li>Checked in .runsettings file</li>
<li>Set build definition to "Custom" and pointed to .runsettings file</li>
</ul>

The build process itself works fine. We can get code coverage results when we build the project locally in the IDE. On the build server, both MSTest and NUnit test projects run fine, and we see pass/fail results as expected. The "No Code Coverage Results" message still plagues us though.

Update 2 -
Here is what we see in the run log:
<img src="https://i.stack.imgur.com/rWxLM.png" alt="Build log test run output">

Somebody suggested homegrown code-coverage calculator in <a href="https://stackoverflow.com/a/16198120/141508">https://stackoverflow.com/a/16198120/141508</a>, but it'd be a crime to spend $150 bazillion-thousand dollars on TFS 2013 &amp; VS Ultimate 2013 with MSDN and still not have this one basic function working.

No code coverage results on TFS 2013 Build Server

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

因此，我们的TFS 2013构建除了报告代码覆盖范围外，一切都做得很正确。我在这里看到过类似的问题，例如，但我们已经尝试了建议的修复，但没有结果。UPDATE 1-我们已经采取了更多的步骤来解决这个问题；下面是完整的列表：确保在构建服务器上安装了Visual终极版尝试将构建定义的"CodeCoverageEnabled...

问TFS 2013 Build Server上没有代码覆盖结果
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问TFS 2013 Build Server上没有代码覆盖结果EN