我最初很难设置maven-failsafe-plugin和JUnit5的集成测试，但现在它可以工作了：
plugins:
- artifactId: maven-failsafe-plugin
groupId: org.apache.maven.plugins
version: 2.19.1
dependencies:
- artifactId: junit-platform-surefire-provider
groupId: org.junit.platform
version: 1.0.3
- artifactId: junit-jupiter-engine
groupId: org.junit.jupiter
version: 5.1.1
configuration:
includes:
- v3api/*IntegrationTests.java
executions:
- goals: [ integration-test, verify ]
但是，我想将神器变成一个胖罐子，似乎spring-boot-maven-plugin与maven-failsafe-plugin发生冲突，因为如果我将此配置放入我的pom中......
- artifactId: spring-boot-maven-plugin
groupId: org.springframework.boot
version: ${spring.boot.version}
executions:
- goals: [ repackage ]
configuration:
fork: true
executable: true
outputDirectory: ${project.build.directory}/binary
然后我在集成测试中收到此错误：
Jun 05, 2018 3:03:15 PM org.junit.platform.launcher.core.DefaultLauncher handleThrowable
WARNING: TestEngine with ID 'junit-jupiter' failed to discover tests
java.lang.NoClassDefFoundError: com/adam/api/DbAccess
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.privateGetPublicMethods(Class.java:2902)
at java.lang.Class.getMethods(Class.java:1615)
at org.junit.platform.commons.util.ReflectionUtils.getDefaultMethods(ReflectionUtils.java:1024)
at org.junit.platform.commons.util.ReflectionUtils.getDeclaredMethods(ReflectionUtils.java:997)
at org.junit.platform.commons.util.ReflectionUtils.findAllMethodsInHierarchy(ReflectionUtils.java:939)
at org.junit.platform.commons.util.ReflectionUtils.findMethods(ReflectionUtils.java:923)
at org.junit.platform.commons.util.ReflectionUtils.findMethods(ReflectionUtils.java:909)
at org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveContainedMethods(JavaElementsResolver.java:189)
at org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveChildren(JavaElementsResolver.java:177)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveClass(JavaElementsResolver.java:61)
at org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.lambda$resolve$3(DiscoverySelectorResolver.java:69)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.resolve(DiscoverySelectorResolver.java:68)
at org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.resolveSelectors(DiscoverySelectorResolver.java:50)
at org.junit.jupiter.engine.JupiterTestEngine.discover(JupiterTestEngine.java:61)
at org.junit.platform.launcher.core.DefaultLauncher.discoverEngineRoot(DefaultLauncher.java:130)
at org.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:117)
at org.junit.platform.launcher.core.DefaultLauncher.discover(DefaultLauncher.java:82)
at org.junit.platform.surefire.provider.TestPlanScannerFilter.accept(TestPlanScannerFilter.java:50)
at org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:98)
at org.junit.platform.surefire.provider.JUnitPlatformProvider.scanClasspath(JUnitPlatformProvider.java:121)
at org.junit.platform.surefire.provider.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:111)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Caused by: java.lang.ClassNotFoundException: com.adam.api.DbAccess
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 28 more
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
在 maven spring 启动文档中，他们描述了如何配置插件以启动和停止 Spring 启动应用程序，以便与pre-和post-integration-testing生命周期阶段进行集成测试。
我的应用程序的生命周期与 docker 和 kubernetes 方面略有不同。它是这样的：
- 包装罐子
- 用弹簧启动插件把罐子变成一个胖罐子
- 目录
- 将其安装到 docker 注册表
- 部署到开发
- 集成测试
- 将构建从开发提升到测试
- 部署到测试
我尝试将 spring 启动插件绑定到package阶段，但这对错误没有影响。
除了 Spring 启动生命周期阶段问题之外，它还可能与 JUnit5 有很大关系，因为 JUnit5 似乎maven-failsafe-plugin几乎不受支持：如何使用 Maven 故障安全插件运行 JUnit 5 集成测试？
我也在Spring plus JUnit Jupiter上看到过这个，但它对集成测试没有帮助。
以下内容对我有用：
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>${springboot.version}</version>
<executions>
<execution>
<!-- repackage will break the integration-test class-path, so schedule after -->
<phase>post-integration-test</phase>
<goals>
<goal>repackage</goal>
</goals>
</execution>
</executions>
</plugin>
我可以通过以下方式运行集成测试：mvn verify
SpringBoot通过以下方式发布：java -jar target/my-jar.jar
我已经在层次结构中使用这些插件完成了此操作：
Parent
|
pom.xml (Added tests plugins including maven-failsafe-plugin)
|
application-startup
|
pom.xml (Added spring-boot-maven-plugin)
通过这种方式，您的所有子项目都将进行测试，并且只有在该之后，maven才会组装在一个胖罐子中。