NOver 1.5.8 确实生成了覆盖报告

发布于 2024-09-27 03:58:57 字数 1125 浏览 1 评论 0原文

我运行 NoverExploler,对其进行配置,因此命令行看起来像这样

"D:\Development\Projects\t.net\lib\NCover\NCover.Console.exe" //reg //w "D:\Development\Projects\t.net\build_output\t.net" //v "D:\Development\Projects\t.net\lib\NUnit\nunit-console.exe" t.Core.Tests.dll /framework=4.0

输出coverage.xml 似乎是空的。同时,如果我通过 Visual Studio(由 TestDriven.Net)运行 Coverate 报告,它会完美生成。

我比较了两种情况的coverage.log 文件。如果我通过 NCoverExporer 运行:

事件:日志链接已建立。 事件:通信链路已建立。 消息:准备好命令输入。 事件:详细日志记录已禁用 事件:启用日志记录 事件:自动排除已启用 消息:监控程序集:(所有加载的程序集) MESSAGE:排除具有以下属性的类型和方法:CoverageExcludeAttribute; 消息:收到驱动程序就绪事件。 消息:v2.0.50727

如果是 TestDriven.net

事件:日志链接已建立。 事件:通信链路已建立。 消息:准备好命令输入。 事件:详细日志记录已禁用 事件:启用日志记录 事件:自动排除已启用 消息:监控程序集:Microsoft.Web.Mvc;Moq;T.Core;T.Core.Tests;Web; MESSAGE:排除具有以下属性的类型和方法:CoverageExcludeAttribute;System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute; 消息:收到驱动程序就绪事件。 消息:v4.0.30319

请参阅监视程序集和消息:v4.0.30319 中的差异。对于 TD.net,它正确地支持 .NET 框架。

有什么线索,如何让 NCover 发挥作用,就像 TD.net 中那样?在哪里配置的?

I run NCoverExploler, configure it, so command line look like this

"D:\Development\Projects\t.net\lib\NCover\NCover.Console.exe" //reg //w "D:\Development\Projects\t.net\build_output\t.net" //v "D:\Development\Projects\t.net\lib\NUnit\nunit-console.exe" t.Core.Tests.dll /framework=4.0

Output coverage.xml appears to be empty. In the same time, if I run Coverate report by Visual Studio (by TestDriven.Net), it generates just perfectly.

I've compared coverage.log files for 2 cases. In case if I run by NCoverExporer:

EVENT: Log link established.
EVENT: Communications link established.
MESSAGE: Ready for command input.
EVENT: Verbose Logging Disabled
EVENT: Logging Enabled
EVENT: AutoExclusion Enabled
MESSAGE: Monitoring Assemblies: (All Loaded Assemblies)
MESSAGE: Excluding Types and Methods with these Attributes: CoverageExcludeAttribute;
MESSAGE: Received driver ready event.
MESSAGE: v2.0.50727

In case of TestDriven.net

EVENT: Log link established.
EVENT: Communications link established.
MESSAGE: Ready for command input.
EVENT: Verbose Logging Disabled
EVENT: Logging Enabled
EVENT: AutoExclusion Enabled
MESSAGE: Monitoring Assemblies: Microsoft.Web.Mvc;Moq;T.Core;T.Core.Tests;Web;
MESSAGE: Excluding Types and Methods with these Attributes: CoverageExcludeAttribute;System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute;
MESSAGE: Received driver ready event.
MESSAGE: v4.0.30319

Please see the difference in Monitoring Assemblies and MESSAGE: v4.0.30319. In case of TD.net, it correctly supples .NET framework.

Any clues, how to make NCover make work, as it in TD.net ? Where is it configured?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

腻橙味 2024-10-04 03:58:57

尝试我在这里找到的答案:强制 NCover 1.5.8 像 testdriven.net 一样使用 v4 框架?

我还使用该问题的其他答案使所有程序与 .net 4 一起运行,但不知道这是否重要。我将调查并更新答案。

我已经用解决方案更新了另一个线程中的答案,我可以使用该解决方案在我的(win 7 x64)机器上启动并运行。希望它会对您有所帮助,我现在在coverage.log 中收到MESSAGE: v4.0.30319

try the answer I found here: Force NCover 1.5.8 to use v4 framework like testdriven.net does?.

I also made all programs run with .net 4 using the other answer to that question, but don't know if that was important or not. I'll investigate and update the answer.

I have updated my answer in the other thread with the solution which I was able to use to get things up and running on my (win 7 x64) machine. Hopefully it will help you, I now get the MESSAGE: v4.0.30319 in my coverage.log.

折戟 2024-10-04 03:58:57

NCover 1.5.8 不支持 .net 4.0,看起来 TD.NET 将 .NET 4 作为默认设置。

NCover 1.5.8 Does not support .net 4.0 and it looks like TD.NET is picking up .NET 4 as the default.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文