运行 Eclipse (EclEmma/JaCoCo) 代码覆盖率时 ByteBuddy 重置失败

ByteBuddy reset fails when running with Eclipse (EclEmma/JaCoCo) Code Coverage

我正在单元测试中使用 ByteBuddy 重新定义 classes。我在每次测试后重置 class 以确保测试之间没有串扰。

ByteBuddy 在 Eclipse IDE 或 运行 maven 命令行中简单地 运行ning 测试时按预期工作。但是如果它在 Eclipse 中 运行 有覆盖,重置 class 会导致以下异常:

java.lang.UnsupportedOperationException: class redefinition failed: attempted to change the schema (add/remove fields)

Bellow 是一个示例测试,它在默认 JUnit 运行ner 中通过,但在 Eclipse 中使用代码覆盖率 运行 时失败。下面是失败的完整堆栈跟踪。

我正在使用 ByteBuddy 版本 1.8.22 和 EclEmma Java 代码覆盖包版本 3.1.0.201804041601。

我假设这个问题是由于 ByteBuddy class 修改和 EclEmma 代码检测之间的冲突造成的。是否有替代方法来恢复 class 定义来解决此问题?

在覆盖范围内失败:

import static net.bytebuddy.matcher.ElementMatchers.named;
import static org.assertj.core.api.Assertions.assertThat;

import org.junit.Test;

import net.bytebuddy.ByteBuddy;
import net.bytebuddy.agent.ByteBuddyAgent;
import net.bytebuddy.dynamic.loading.ClassReloadingStrategy;
import net.bytebuddy.implementation.FixedValue;

public class ByteBuddyEclEmmaTest {

    @Test
    public void recreateEclEmmaByteBuddyResetIssue() throws Exception {

        ByteBuddyAgent.install();

        ByteBuddy byteBuddy = new ByteBuddy();
        ClassReloadingStrategy classReloadingStrategy = ClassReloadingStrategy.fromInstalledAgent();

        byteBuddy
                .redefine(X.class)
                .method(named("getValue")).intercept(FixedValue.value("faked value"))
                .make()
                .load(X.class.getClassLoader(), classReloadingStrategy);

        X x = new X();
        assertThat(x.getValue()).isEqualTo("faked value");

        classReloadingStrategy.reset(X.class);

        assertThat(x.getValue()).isEqualTo("real value");
    }

    public class X {

        public String getValue() {

            return "real value";
        }
    }
}

堆栈跟踪:

java.lang.UnsupportedOperationException: class redefinition failed: attempted to change the schema (add/remove fields)
    at sun.instrument.InstrumentationImpl.redefineClasses0(Native Method)
    at sun.instrument.InstrumentationImpl.redefineClasses(InstrumentationImpl.java:170)
    at net.bytebuddy.dynamic.loading.ClassReloadingStrategy$Strategy.apply(ClassReloadingStrategy.java:261)
    at net.bytebuddy.dynamic.loading.ClassReloadingStrategy$Strategy.reset(ClassReloadingStrategy.java:279)
    at net.bytebuddy.dynamic.loading.ClassReloadingStrategy.reset(ClassReloadingStrategy.java:209)
    at net.bytebuddy.dynamic.loading.ClassReloadingStrategy.reset(ClassReloadingStrategy.java:195)
    at ByteBuddyEclEmmaTest.recreateEclEmmaByteBuddyResetIssue(ByteBuddyEclEmmaTest.java:30)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.junit.runners.model.FrameworkMethod.runReflectiveCall(FrameworkMethod.java:50)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:290)
    at org.junit.runners.ParentRunner.schedule(ParentRunner.java:71)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
    at org.junit.runners.ParentRunner.access[=14=]0(ParentRunner.java:58)
    at org.junit.runners.ParentRunner.evaluate(ParentRunner.java:268)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:538)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:760)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:460)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:206)

我发现我的问题是由旧版本的 ByteBuddy 引起的。我正在从 Mockito 将 1.6.14 版本拉入我的项目。当我明确引入 ByteBuddy 版本 1.8.22 时,测试成功运行,无论是否有 Coverage。