You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>${surefire.version}</version>
<configuration>
<workingDirectory>.</workingDirectory>
<forkCount>0</forkCount>
<!-- both config values make sure the tests pass in a controlled fashion -->
</configuration>
</plugin>
The text was updated successfully, but these errors were encountered:
Not entirely sure how to replicate this as it is currently working on all of our GitHub actions. When we add your workaround it breaks things, so we don't want to do that. We'd be happy to join a call with you to understand the issue better.
Problem
when running approval tests (JUnit5, Java 17) from
mvn test
via themaven-surefire-plugin
, the tests fail withwith maven, approvals and the plugin being latest ones. Earlier surefire plugin versions did not produce an insight into this stacktrace.
In IntelliJ the test run succeeds without any changes. Surefire seems to have a test run isolation feature, enabling the forks which might need a special treatment by approvals.
A work-around which helped me proceed: ↓
Workaround
The text was updated successfully, but these errors were encountered: