单元测试CDI与CDI单元Jglue

我们希望使用Jglue框架来单元测试我们的CDI应用程序。我们使用gradle来建造。单元测试CDI与CDI单元Jglue

我们准备了这样的事情：

1）班进行测试：

@Default 
public class RateTypeHibernateFactory implements RateTypeFactory { 

@Override 
public RateType getInstance(String name, String description) { 
    RateType rateType = getInstance(); 
    rateType.setName(name); 
    rateType.setDescription(description); 
    return rateType; 
} 

}

2）接口：

public interface RateTypeFactory { 

public RateType getInstance(String name, String description); 

}

3）摇篮设置（我们遵循入门http://jglue.org/cdi-unit/）

dependencies { 

    testCompile (group: 'junit', name: 'junit', version: '4.8.2') 
    testCompile (group: 'org.jglue.cdi-unit', name: 'cdi-unit', version: '2.2.0') 

}

4）测试类：

@RunWith(CdiRunner.class) 
public class RateTypeFactoryTest { 

@Inject RateTypeFactory rateTypeFactory; 

@Test 
public void testGetInstance() { 
    RateType rateType = rateTypeFactory.getInstance(); 
    assertNotNull(rateType); 
} 

}

当我们运行这个简单的测试中，我们始终得到此异常：

com.etnetera.projects.ticketing.model.factory.RateTypeFactoryTest > testGetInstance FAILED 
java.lang.NoSuchMethodError 

1 test completed, 1 failed 
:test FAILED

在/build/reports/tests/index.html有：

java.lang.NoSuchMethodError: org.jboss.weld.metadata.BeansXmlImpl.<init>(Ljava/util/List;Ljava/util/List;Ljava/util/List;Ljava/util/List;Lorg/jboss/weld/bootstrap/spi/Scanning;Ljava/net/URL;Lorg/jboss/weld/bootstrap/spi/BeanDiscoveryMode;Ljava/lang/String;)V 
at org.jglue.cdiunit.internal.WeldTestUrlDeployment.<init>(WeldTestUrlDeployment.java:80) 
at org.jglue.cdiunit.CdiRunner$1.createDeployment(CdiRunner.java:71) 
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:137) 
at org.jglue.cdiunit.CdiRunner.createTest(CdiRunner.java:82) 
at org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:258) 
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) 
at org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:255) 
at org.jglue.cdiunit.CdiRunner.methodBlock(CdiRunner.java:113) 
at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) 
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) 
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) 
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) 
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) 
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) 
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) 
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) 
at org.junit.runners.ParentRunner.run(ParentRunner.java:236) 
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:55) 
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:42) 
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:71) 
at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:49) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:597) 
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) 
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) 
at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) 
at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) 
at $Proxy2.processTestClass(Unknown Source) 
at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:103) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:597) 
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) 
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) 
at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:355) 
at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
at java.lang.Thread.run(Thread.java:662)

请没有任何人知道如何避免这种例外？如果需要，我可以添加更多的细节。

来源

2013-10-23 Vojtěch Ruschka

你运行对什么版本的焊缝的提取物？ –

我的焊缝版本是1.1.8。 –

1.1.8应与2.1.1 工作，如果你仍然有问题，那么请提高对问题跟踪了一个错误：https://github.com/BrynCooke/cdi-unit/issues?state=open – Bryn

这通常是由焊接的不支持的版本引起的被使用。但是，我刚刚发布了CDI-Unit 2.2.1，它修复了Gradle构建中的一些问题。请你可以试试吗？

来源

2013-11-08 11:09:17 Bryn

还要检查出Gradle示例项目： https://github.com/BrynCooke/cdi-unit/tree/master/cdi-unit-tests-gradle – Bryn

似乎你调用该接口上的一个方法没有参数。而不是 RateType rateType = rateTypeFactory.getInstance(); 你应该叫 RateType rateType = rateTypeFactory.getInstance("name", "description");

也许我错过了什么gradle这个有关？

来源

2015-10-22 14:20:55 jvalli

我也遇到了类似的问题（一个错误信息有点不同）。我围绕这个问题搜索了很多东西，但没有发现太多关于这个问题，所以我得出结论，这是我的项目特有的。这导致我怀疑项目依赖关系之间的版本不匹配。

我使用weld-servlet: 2.4.0.Final作为compile依赖项，而cdi-unit: 3.1.4作为test依赖项。我注意到cdi-unit对weld-se-core: 2.3.2.Final有依赖。因此，我将weld-se-core添加到我的依赖管理中，其版本与我的weld-servlet工件相同，并解决了问题。

有关进一步的参考，这是我pom.xml文件

<properties> 
    <weld.version>2.4.0.Final</weld.version> 
    <cdi-unit.version>3.1.4</cdi-unit.version> 
    (...) 
</properties> 

<dependencyManagement> 
    <dependencies> 
     <!-- CDI --> 
     <dependency> 
      <groupId>org.jboss.weld.servlet</groupId> 
      <artifactId>weld-servlet</artifactId> 
      <version>${weld.version}</version> 
     </dependency> 
     <!-- Tests --> 
     <dependency> 
      <groupId>org.jglue.cdi-unit</groupId> 
      <artifactId>cdi-unit</artifactId> 
      <version>${cdi-unit.version}</version> 
      <scope>test</scope> 
     </dependency> 
     <dependency> 
      <groupId>org.jboss.weld.se</groupId> 
      <artifactId>weld-se-core</artifactId> 
      <version>${weld.version}</version> 
      <scope>test</scope> 
     </dependency> 
     (...) 
    </dependencies> 
</dependencyManagement> 

<dependencies> 
    <!-- CDI --> 
    <dependency> 
     <groupId>org.jboss.weld.servlet</groupId> 
     <artifactId>weld-servlet</artifactId> 
    </dependency> 
    <!-- Tests --> 
    <dependency> 
     <groupId>org.jglue.cdi-unit</groupId> 
     <artifactId>cdi-unit</artifactId> 
    </dependency> 
    (...) 
</dependencies>

来源

2016-10-21 08:57:15 Aldian

单元测试CDI与CDI单元Jglue

回答

相关问题