Get an ERROR executing surefire/cucumber test (NoSuchMethodError -> getFirstElement()) after update junit-platform-suite 1.10.3 to 1.11.0 #3995
Replies: 1 comment 4 replies
-
|
Looks like your build is pulling in a pre-1.11 version of junit-platform-commons. Is this a Spring (Boot) project? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply <3 No, it is not. We are building a jar and start with class: KomponententestCucumber (see below) But... after your reply, I checked all our other own (xyz-) libs once again and there is one candidate, which uses JUnit 4, what we have not noticed before :-(... I have to update the POM too, and rebuild the lib and test again. I will report back here when I have more information. Positive and negative. <properties>
<xyz-common.version>6.5.19</xyz-common.version>
<xyz-common-test.version>4.4.2</xyz-common-test.version>
<maven-surefire-plugin.version>3.5.0</maven-surefire-plugin.version>
<maven-compiler-plugin.version>3.13.0</maven-compiler-plugin.version>
<maven-deploy-plugin.version>3.1.3</maven-deploy-plugin.version>
<maven-jar-plugin.version>3.4.2</maven-jar-plugin.version>
<lombok.version>1.18.34</lombok.version>
<xyz-library.version>0.7.2</xyz-library.version>
<cucumber.version>7.18.1</cucumber.version>
<pdfbox.version>3.0.3</pdfbox.version>
<qpid-jms-client.version>2.5.0</qpid-jms-client.version>
<jsoup.version>1.18.1</jsoup.version>
<junit-jupiter.version>5.11.0</junit-jupiter.version>
<!-- the version 1.11.0 seems to be incompatible with surefire 3.5.0. Check later if this issue is fixed with newer versions of either libraries-->
<!-- a discussion at github started: https://github.com/junit-team/junit5/discussions/3995 -->
<junit-platform.version>1.11.0</junit-platform.version>
<assertj.version>3.26.3</assertj.version>
<guava.version>33.3.0-jre</guava.version>
<apache-commons-collections.version>4.4</apache-commons-collections.version>
<target.repo>blabla-maven-stage-dev-local</target.repo>
</properties>@Suite
@IncludeEngines("cucumber")
@ConfigurationParameter(key = PLUGIN_PROPERTY_NAME, value = "json:target/KomponententestCucumber.json, html:target/cucumber-reports/report.html, timeline:target/timeline, rerun:target/rerun.txt")
@ConfigurationParameter(key = FEATURES_PROPERTY_NAME, value = "src/test/resources/features/komponententest")
public class KomponententestCucumber {
} |
Beta Was this translation helpful? Give feedback.
-
|
Since you're using Cucumber, it could be that |
Beta Was this translation helpful? Give feedback.
-
|
OMG that's it, many thanks @marcphilipp! I have to test the services now, but I think that will work. |
Beta Was this translation helpful? Give feedback.
-
|
It works fine also in the pipeline. Many thanks again 🥇. I am closing the discussion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Has someone the same problem as described below?
Thanks in advance for any comment!
I tried to update the junit-platform-suite version from 1.10.3 (old) to 1.11.0 (new)
With the following "old" configuration cutout: POM.xml
In the console we are executing the test by:
After build was successful, it starts the tests and the output is like:
`...
[INFO]
[INFO] --- maven-surefire-plugin:3.5.0:test (default-test) @ komponententest ---
[INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
Picked up JAVA_TOOL_OPTIONS: -Duser.language=en -Duser.country=US
Sep 15, 2024 7:23:03 PM io.cucumber.junit.platform.engine.DiscoverySelectorResolver warnWhenCucumberFeaturesPropertyIsUsed
WARNING: Discovering tests using the cucumber.features property. Other discovery selectors are ignored!
This is a work around for the limited JUnit 5 support in Maven and Gradle. Please request/upvote/sponsor/ect better support for JUnit 5 discovery selectors. For details see: cucumber/cucumber-jvm#2498
If you are using the JUnit 5 Suite Engine, Platform Launcher API or Console Launcher you should not use this property. Please consult the JUnit 5 documentation on test selection.
[INFO] Running de.db.xxxxx.yyy.features.runners.KomponententestCucumber
[INFO] Running io.cucumber.junit.platform.engine.CucumberTestEngine
...
`
==> This works!
Now I update the junit-platform-suite version to 1.11.0 (new):
and in the console:
the build step
Cutout of the detailed output:
Beta Was this translation helpful? Give feedback.
All reactions