I'm currently working on updating my WireMock work...
# wiremock-javab
Bas Dijkstra
10/18/2025, 7:31 AMI'm currently working on updating my WireMock workshop (https://github.com/basdijkstra/wiremock-workshop), and I'd like to use WireMock 4 in the next version. The latest beta
4.0.0-beta.155.13.4t
Tom
10/21/2025, 9:15 AMThanks for pointing this out Bas. We haven’t had any time to look at JUnit 6 compatibility yet (we’re up against it with customer commitments for the moment), but clearly this is very important so we’ll take a look as soon as there’s a break available.
b
Bas Dijkstra
10/21/2025, 10:34 AMNo problem, thanks for the response!
👍 1
t
Tom
11/17/2025, 11:46 AM@Bas Dijkstra looking at JUnit 6 compat now. JUnit 5 tests all pass apart from two when I bump to 6.0.0 of JUnit so I’m wondering what problems you encountered when you tried it?
If I take your workshop project and bump the JUnit version will that reproduce the failure?
b
Bas Dijkstra
11/17/2025, 4:19 PMYeah I think that’s where I ran into the issue
t
Tom
11/17/2025, 5:11 PMOK, I’ll try that. Currently the only problem I’m seeing is quite niche - getting wrong port numbers when using @Nested test classes.
Tom
11/17/2025, 9:16 PMI’m seeing exactly the same results when I switch your project to JUnit 6.0.1.
I did have to add a couple of dependencies to make the Maven build run the tests properly. This is what my
pom.xml Copy code
<project xmlns="<http://maven.apache.org/POM/4.0.0>" xmlns:xsi="<http://www.w3.org/2001/XMLSchema-instance>"
xsi:schemaLocation="<http://maven.apache.org/POM/4.0.0> <http://maven.apache.org/xsd/maven-4.0.0.xsd>">
<modelVersion>4.0.0</modelVersion>
<groupId>com.ontestautomation.workshops.wiremock</groupId>
<artifactId>wiremock-workshop</artifactId>
<version>1.0.0</version>
<description>Project containing examples, exercises and answers for my open source WireMock workshop</description>
<properties>
<maven.compiler.release>17</maven.compiler.release>
<wiremock.version>4.0.0-beta.15</wiremock.version>
<junit.version>6.0.1</junit.version>
<restassured.version>5.5.6</restassured.version>
<slf4j.version>2.0.17</slf4j.version>
<maven.surefire.plugin.version>3.5.4</maven.surefire.plugin.version>
</properties>
<dependencies>
<dependency>
<groupId>org.wiremock</groupId>
<artifactId>wiremock</artifactId>
<version>${wiremock.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-engine</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-params</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.platform</groupId>
<artifactId>junit-platform-launcher</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.platform</groupId>
<artifactId>junit-platform-commons</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>io.rest-assured</groupId>
<artifactId>rest-assured</artifactId>
<version>${restassured.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-nop</artifactId>
<version>${slf4j.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.13.0</version>
<configuration>
<release>${maven.compiler.release}</release>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>${maven.surefire.plugin.version}</version>
</plugin>
</plugins>
</build>
</project>b
Bas Dijkstra
11/18/2025, 11:33 AMThanks! I’ll have a look tonight and see if I can make it work, too
t
Tom
11/18/2025, 11:34 AMSome tests were failing - I’m not sure if this was by design or not. But the same ones were failing regardless of the JUnit version, it seemed.
b
Bas Dijkstra
11/18/2025, 11:35 AMYes, the exercises are basically in the ‘write the mock to make the test pass’ format, this is by design :)
Bas Dijkstra
11/18/2025, 5:03 PMThat did the trick, thank you very much, @Tom!
👍 1
30 Views