blocks|key|2544559|text|这是一个已知的问题与依克勒玛(JaCoCo)。基本上，这两个库都修改字节代码，但Mockito在运行时对其进行修改，从而生成不同的二进制.class文件。显然，JaCoCo通过一个hashMap跟踪它正在观察的类，hashMap的哈希代码是由类定义派生的，所以在Mockito修改类之后，哈希代码就会有所不同，这样JaCoco就不能在它的内部地图中找到类了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2544560|更详细地讨论：|2544561|为什么EclEmma不使用@RunWith(PowerMockRunner.class)的测试覆盖代码|offset|length|2544562|使用JUnit和Powermock的艾玛代码覆盖率|2544563|http://code.google.com/p/powermock/issues/detail?id=402|2544564|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9726212/why-tclemma-doesnt-coverage-code-with-tests-with-runwithpowermockrunner-class|1|https://stackoverflow.com/questions/17957496/emma-code-coverage-with-junit-and-powermock|2^0|0|0|0|1F|0|0|0|P|1|0|0|1J|2|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@$F|13|G|14|1|15]]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@$F|17|G|18|1|19]]|A|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|K]]]]

This is a known problem with Eclemma (JaCoCo). Basically both libraries modify byte code but Mockito modifies it during runtime which produces a different binary .class file. JaCoCo apparently uses keeps track of the classes it's watching via a hashMap whose hashcode is derived by the class definition so the hashcode will be different after Mockito modifies the class so JaCoco can't find the class in it's internal Maps anymore.

Discussed in more detail:

<a href="https://stackoverflow.com/questions/9726212/why-tclemma-doesnt-coverage-code-with-tests-with-runwithpowermockrunner-class">Why EclEmma doesn&#39;t coverage code with tests with @RunWith(PowerMockRunner.class)</a>

<a href="https://stackoverflow.com/questions/17957496/emma-code-coverage-with-junit-and-powermock">Emma code coverage with JUnit and Powermock</a>

<a href="http://code.google.com/p/powermock/issues/detail?id=402" rel="nofollow noreferrer">http://code.google.com/p/powermock/issues/detail?id=402</a>

blocks|key|1109872|text|根据此链接上一次更新，更新EclEmma插件(通过卸载和重新安装)以及最新的PowerMock和Mockito+(3.7)解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1109873|这个变更日志证实了这一点。|1109874|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jayway/powermock/issues/422|1|https://raw.githubusercontent.com/jayway/powermock/master/changelog.txt^0|2|3|0|0|2|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Per <a href="https://github.com/jayway/powermock/issues/422" rel="nofollow">this link</a> last update, updating EclEmma plugin (by Uninstalling and Reinstalling) along with latest PowerMock and Mockito JARs in Eclipse (3.7) resolved the issue.

This <a href="https://raw.githubusercontent.com/jayway/powermock/master/changelog.txt" rel="nofollow">change log</a> confirms that.

blocks|key|2544620|text|Powermock适用于依莱玛1.5.3，但不适用于最新的EclIMA3.0.0！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2544621|日食-开普勒服务第2版JUnit4+PowerMockito2+-+1.7.0.引理1.5.3|2544622|下面给出的步骤是有效的，在运行junit测试时，我可以看到非零覆盖率。|2544623|从http://www.eclemma.org/download.html下载引理-1.5.3.zip|ordered-list-item|2544624|将内容解压缩到本地文件夹(引理-1.5.3)|2544625|将此路径添加到菜单栏:窗口->首选项->安装/更新->可用软件站点|2544626|帮助->在“with+with”中安装新软件->，选择新条目(在prev中添加)。步骤)|2544627|一个接一个地取消选中复选框，然后将显示“”插件选项。引理覆盖选项将显示在选择窗口中。|2544628|继续到下一个并完成..。|2544629|好好享受！|2544630|entityMap|0|LINK|mutability|MUTABLE|url|http://www.eclemma.org/download.html^0|0|15|0|0|0|1|10|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|M|3|N|5|L|7|1F|8|@]|D|@]|E|$]]|$1|O|3|P|5|L|7|1G|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1H|8|@]|D|@]|E|$]]|$1|S|3|T|5|L|7|1I|8|@]|D|@]|E|$]]|$1|U|3|V|5|L|7|1J|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1K|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|15]]]]

Powermock works well with Eclemma 1.5.3; but doesn't work with latest Eclemma 3.0.0 !!

Eclipse - Kepler Service release 2
JUnit4
PowerMockito2 - 1.7.0. 
Eclemma 1.5.3

The below given steps are working and I am able to see non-zero coverage % on running junit tests.

<ol>
<li>Download eclemma-1.5.3.zip from <a href="http://www.eclemma.org/download.html" rel="nofollow noreferrer">http://www.eclemma.org/download.html</a></li>
<li>Extract the contents to a local folder (eclemma-1.5.3)</li>
<li>Add this path to Menu bar : Window -> Preferences -> Install/Update -> Available Software Sites</li>
<li>Help -> Install New Software -> in "Work with" drop down, select the new entry (added in prev. step)</li>
<li>Uncheck the check boxes one after another then the "Eclemma Coverage" plugin options will be shown. Eclemma Coverage option will be shown in selection window.</li>
<li>Proceed to next and complete...</li>
</ol>

Enjoy !!!

blocks|key|2544663|text|EclEmma修改字节码以检测代码覆盖率，就像PowerMock所做的那样，以允许您运行不可访问的代码。这两个更改都是不兼容的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2544664|解决方案是使用PowerMock提供的运行程序来解决这种不兼容问题。|2544665|http://www.notonlyanecmplace.com/make-eclemma-test-coverage-work-with-powermock/|offset|length|2544666|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|28|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

EclEmma modifies bytecode to detect code coverage as PowerMock does to allow you to run an inaccessible code. Both changes are incompatible

The solution is to use a runner offered by PowerMock which workaround that incompatibility

<a href="http://www.notonlyanecmplace.com/make-eclemma-test-coverage-work-with-powermock/" rel="nofollow noreferrer">http://www.notonlyanecmplace.com/make-eclemma-test-coverage-work-with-powermock/</a>

I met a problem of using EclEmma plugin in Eclipse.
It doesn't show code coverage when I use annotation <code>@RunWith</code> passing <code>(PowerMockRunner.class)</code> as an argument. In case of using <code>(MockitoJUnitRunner.class)</code> everything is fine.
Waiting for your suggestions? :)

EclEmma code coverage plugin and PowerMockRunner

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我遇到了在Eclipse中使用EclEmma插件的问题。当我使用注释@RunWith传递(PowerMockRunner.class)作为参数时，它不会显示代码覆盖率。如果使用(MockitoJUnitRunner.class)，一切都很好。等待你的建议？)

问EclEmma代码覆盖插件和PowerMockRunner
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问EclEmma代码覆盖插件和PowerMockRunnerEN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问EclEmma代码覆盖插件和PowerMockRunner
EN