-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run Glacio and Cucumber in the same project #2
Comments
Thanks for the feedback early-tester 😄 It seems that you removed too much. Currently the project you provided uses an old version of the maven-surefire-plugin (2.12.4 by default), only compatible with JUnit4. In this configuration, only Cucumber can run as JUnit4 cannot run the Glacio engine, built for JUnit-Platform (platform appearing with JUnit5). To solve your issue, I would :
A word of caution however: as junit-platform is evolving quickly, they may be some breaking changes, In order to work properly, I would keep the same version of the platform used by Glacio for now so, adding to your pom.xml: <dependencies>
...
<dependency>
<groupId>org.junit.vintage</groupId>
<artifactId>junit-vintage-engine</artifactId>
<version>5.3.2</version> <!-- not 5.4.1, which will not be able to run Glacio engine (still using 5.3.2) -->
<scope>test</scope>
</dependency>
</dependencies>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>${maven-surefire-plugin.version}</version>
</plugin>
</plugins>
</pluginManagement>
</build> should do the trick |
Perfect ! Thanks ;) |
Hello Loic,
While trying to toy around Glacio, I wanted to compare and run Cucumber tests and Glacio tests in the same project but didn't succeed to do it.
Base on this example project, I removed every thing :
And made 2 commits :
Can you help me on this ?
Since I'm not used to junit test engines, what am I missing ?
Thank you very much :)
The text was updated successfully, but these errors were encountered: