Hi Team, We are looking for an option to tag PACT tests with a specific identifier/version. The use case is having a version already promoted to PROD which should use say version x for provider verification and version y for PACTS being written for provider that is still in DEV. How can we specifically tag the PACT file and have the provider select PACTS only corresponding to that version, so that there are no issues running the PACT tests across multiple branches/deployments. Any specific examples for both configuration on consumer side as well as producer side would help.

Hello. I am trying to create a synchronous message pact consumer test. I have defined the pact context and am working on the corresponding consumer test:

@Test
    @PactTestFor(pactMethod = "mySyncMessagePact")
    void mySyncMessagePact(V4Interaction.SynchronousMessages interaction) {
      String request = "{}"; // 1: should call a method that produces the request
      // 2: Validate that the request is okay according to the pact
      // 3: Validate that the response message can be handled
    }

How do I validate that the request message is compliant with the pact that I specified? After looking at the library code I could not find a standard utility that allows me to easily validate this

If I have the

@AllowOverridePactUrl

annotation set, how do I run that test class as part of my regular pipeline? It works fine when I get a request from a webhook, but I don't know how to create the appropriate URLs when running from my build pipeline. Am I confused about something?

Hi Team, Greetings of the day!! I am setting up a Pact contract test for Kafka (MessagePact) and need some guidance. Do we need to spin up a real Kafka instance when writing a consumer contract test? Also, is a Kafka instance required for provider verification? If there are any examples available, please share them. Thanks.

Greetings! I am validating a reasonable complex JSON return from a service (which I hope to simplify moving forward), but I am running into a matching issue: One of the nested objects has a unique name (not standardized), based on the request. In the below example, "ABCD32" is the name, but in a different call, it may be something else.

{
  "plans": {
    "ABCD32": {
      "idRequired": true,
      "ids": [
        "1234"
      ]
    }
  }
}

I'm trying to use

object(<name>)

for this, but the name isn't generally predictable.

rootResponseObject.object("plans", (plans) ->
    plans.object("??????", (plan) -> {
         ratePlan.booleanType("idRequired", true);
         ratePlan.array("ids", (item) -> item.stringType("12345"));
    })
);

I think I'm a bit confused on when we want things to be more general, and when "test by example" is the right way to go. Since I control the request and data, should I just match to that exact string as the result that fulfills the example?

Hello everyone, I have a question about provider states it may be a bit general but since we are implementing pact with pact-jvm I post it here. Please let me know if I should post it elsewhere. When we have a provider state on an interaction that is not implemented in the provider verifier, it will fall in the default case. As a result our server doesn't behave as expected and we might not know right away that it comes from our "dummy" provider state. This lead to some painful debugging. I understand it might not be easy to workaround but I wanted to have your take on this ? Thanks in advance

Hi, I am currently trying to use an Object containing Jodatime as a parameter. unfortunately I then get the error:

java.lang.IllegalAccessException: class kotlin.reflect.jvm.internal.calls.CallerImpl$FieldGetter cannot access a member of class org.joda.time.LocalDate with modifiers "private final"
kotlin.reflect.full.IllegalCallableAccessException: java.lang.IllegalAccessException: class kotlin.reflect.jvm.internal.calls.CallerImpl$FieldGetter cannot access a member of class org.joda.time.LocalDate with modifiers "private final"
	at kotlin.reflect.jvm.internal.KCallableImpl.call

Any idea what I can do? Can I use my own serializer, eg. objectMapper?

So, I'm trying to wrap my head around branches, especially on the provider side. I used to verify my contracts using

mvn

, and because my provider is a Spring service, this works fine:

mvn clean "-Dpact.verifier.publishResults=true" "-Dpact.provider.version=1.0.0-address-ee07f8c04721b90be743fc1c08946663f01e6e46" test

However, I now also want to list the provider branch, but when I try this (following the docs):

mvn clean "-Dpact.verifier.publishResults=true" "-Dpact.provider.version=1.0.0-address-ee07f8c04721b90be743fc1c08946663f01e6e46" "-Dpactbroker.providerBranch=main" test

It does not record the provider branch. Any ideas? Is this even important? I know I will need it in the next step, when I'll introduce pending pacts...

👋 Hello, team! I am trying to setup a sample PACT project with spring boot. After adding the below dependency for the pact concumer I found that one of the class is missing in dependency Dependency

<dependency>
    <groupId>au.com.dius.pact.consumer</groupId>
    <artifactId>junit5</artifactId>
    <version>4.3.6</version>
    <scope>test</scope>
</dependency>

Class

@au.com.dius.pact.consumer.junit5.Pact

Any suggestion on how I could resolve this ?

Hello everyone, I'm looking for some clarity on what stringType() and numberType() methods are matching on using them to construct a jsonBody. My provider is verifying the pact generated using this method but it's using the example parameter as the literal value to compare against. For example i see error messages like "1.14) body: $payment.paymentAmount Expected null (Null) to be an integer" when providing something like .object("payment").numberType("paymentAmount").closeObject(). Any ideas?

Hi team!, can you please help me understand why I am getting this error, my builder is return V4Pact also ?

java.lang.UnsupportedOperationException: Method createPact does not conform required method signature 'public au.com.dius.pact.core.model.V4Pact xxx(PactBuilder builder)'
 at au.com.dius.pact.consumer.junit.JUnitTestSupport.conformsToSignature(JUnitTestSupport.kt:35)
 at au.com.dius.pact.consumer.junit5.PactConsumerTestExt.lookupPact(PactConsumerTestExt.kt:504)
 at au.com.dius.pact.consumer.junit5.PactConsumerTestExt.setupPactForTest(PactConsumerTestExt.kt:270)
 at au.com.dius.pact.consumer.junit5.PactConsumerTestExt.setupMockServerForProvider(PactConsumerTestExt.kt:248)
 at au.com.dius.pact.consumer.junit5.PactConsumerTestExt.beforeTestExecution(PactConsumerTestExt.kt:223)
 at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
 at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)

I was reading on pending pacts and how to use with Pact JVM. The system properties mention that besides setting pactbroker.enablePending = true you also have to provide pactbroker.providerBranch or pactbroker.providerTags. Why is that? The language agnostic doc does not mention anything about that.

Hi, I have created couple of consumer tests using Junit5, they pass and generate pacts also, but when I run either of them, I get this error at class level

java.lang.AssertionError: The following methods annotated with @Pact were not executed during the test: RulesApiConsumerTest.createPactFor200

If these are currently a work in progress, add a @Disabled annotation to the method

I don't see this error when I run them together I have also used

PactTestFor

to categorize the tests with their respective method inside my test class

Hi, We are having some intermittent issues when publishing consumer contracts. We are getting the below error in CI:

Request to path '**********************************************contracts/publish' failed with HTTP response 500
JSON Response:
{
  "error": {
    "message": "source sequence is illegal/malformed utf-8",
    "reference": "YeJQYFKhHV"
  }
}

I think its related to use using the

.matchQuery("version", "1.0.0")

as the value become encoded and then shows as

"1\uB0D60\uB3DA0"

in the contract. We also have a header using

.matchHeader("header", ".*")

which becomes encoded itself and then appears in the broker as

"屏啾"

. We are publishing using the pact gradle plugin and the command

./gradlew pactPublish

. Weirdly though, the pipeline failed twice to publish and then with a retry for a third time it passed. I have suggested to the team to use

encodedQuery

and to change the header value as its not important for the service we are using but I’m curious to know why it would fail to publish but then eventually pass with no changes, is there some sort of race condition there?

Release - 4_7_0-beta_1 New release published by rholshausen ## Upgrade Kotlin to 2.1 and update all dependencies • 7d50d98 - chore: Upgrade KTor to 3.1.3 #1863 • d17e612 - chore(compatibility-suite): Upgrade cucumber to latest • d015fa1 - chore: Update dependencies for all provider modules • 2fd11ab - chore: Update dependencies for all consumer modules • abe80d7 - chore: Update dependencies for all core modules • 52f0e8f - chore: Update codenarc and re-enable detekt • b090143 - chore: Upgrade all core dependencies #1863 • 751614f - chore: Correct CI build • 62ca919 - chore: Upgrade Kotlin to 2.1.21 #1863 • b365641 - fix: Only coerce strings to numbers when comparing headers and query parameters • 1b1cf84 - chore(compatibility-suite): Correct the shared steps after updating the compatibility suite • 8c5b0b1 - fix: Only split values of known multi-value headers #1852 • d7d3030 - fix: Matching rule paths for fields with only digits should not be written as indices #1851 • 5dba442 - fix: Lambda based DSL stringType method did not match the old DSL #1850 • 287b16c - feat: Pass any transport config to the plugin in the test context under the transport_config key • 80d8a87 - chore: Add example of a test with a pending interaction • 2d20163 - fix: Dependency conflict with org.slf4j:slf4j-api was causing Spring tests to fail • 38c0d27 - feat: Update LambdaDsl.newJsonArray to allow setting the number of examples • 19c663c - chore: The pact-jvm-server main spec was not configured correctly • 147a2a6 - fix: LambdaDslJsonArray has no datetime function #1839 • c791170 - chore: Update readme pact-foundation/pact-jvm

Hi Folks, hope you're doing well. Please let me know if someone has encountered it. In pact, I have written a consumer contract and published it to pact broker, and that contract has 3 endpoints in it. Now in provider application I have 3 profiles and each profile is configured to one endpoint. I will be running my provider tests against only one profile at a time, and other 2 profile endpoints shouldn't get validated. How I can handle that in provider application. (In Spring boot)

Looking for a working example of Pact contract tests with Feign Client (consumer side) Hi everyone! 👋 I’m currently working on setting up Pact contract tests for a consumer using Feign Client and was wondering if anyone has a recent, working example to share. I’ve found a few examples online, but many seem outdated or don’t quite match our setup. If you’ve implemented this recently or know of a good reference, I’d really appreciate any pointers! Thanks in advance! 🙏

👋 Hello, team! I’m starting to implement Contract Testing in our organization using Bazel Mono-repo with Pact. Has anyone set this up before or worked with Pact in a Bazel environment? I would appreciate any guidance. Issue: My test is running using a sandbox path, which gets deleted once the tests complete. I’ve tried changing the path using

pact.rootDir

and other configurations, but I’m still facing the same issue. Even after adding

sleep

before and after running the test cases, the tests pass, but the Pact contract file is not being generated. Any help or pointers on how to resolve this would be greatly appreciated. Thanks in advance! Logs when running TestCase (also looked for the path, by adding a print statement - but failed)

bazel test --nocache_test_results //access-control/contracts/openapi/v1:AccessControlConsumerPactTest 

INFO: Invocation ID: 16bab404-9cf2-4e69-88d9-c46f58ef4b02
INFO: Analyzed target //access-control/contracts/openapi/v1:AccessControlConsumerPactTest (0 packages loaded, 252 targets configured).
INFO: Found 1 test target...
INFO: From Testing //access-control/contracts/openapi/v1:AccessControlConsumerPactTest:
==================== Test output for //access-control/contracts/openapi/v1:AccessControlConsumerPactTest:
OpenJDK 64-Bit Server VM warning: Ignoring option --illegal-access=debug; support was removed in 17.0
JUnit4 Test Runner
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by com.google.testing.junit.runner.junit4.JUnit4Runner (file:/private/var/tmp/_bazel_imrankhan/b141c088e4409f9b6c4d0f13116258fa/external/remote_java_tools/java_tools/Runner_deploy.jar)
WARNING: Please consider reporting this to the maintainers of com.google.testing.junit.runner.junit4.JUnit4Runner
WARNING: System::setSecurityManager will be removed in a future release
.SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See <http://www.slf4j.org/codes.html#StaticLoggerBinder> for further details.
Pact files will be written to: /private/var/tmp/_bazel_imrankhan/b141c088e4409f9b6c4d0f13116258fa/sandbox/darwin-sandbox/28/execroot/harness_monorepo/bazel-out/darwin_arm64-fastbuild/bin/access-control/contracts/openapi/v1/AccessControlConsumerPactTest.runfiles/harness_monorepo/pacts
.Pact files will be written to: /private/var/tmp/_bazel_imrankhan/b141c088e4409f9b6c4d0f13116258fa/sandbox/darwin-sandbox/28/execroot/harness_monorepo/bazel-out/darwin_arm64-fastbuild/bin/access-control/contracts/openapi/v1/AccessControlConsumerPactTest.runfiles/harness_monorepo/pacts
.Pact files will be written to: /private/var/tmp/_bazel_imrankhan/b141c088e4409f9b6c4d0f13116258fa/sandbox/darwin-sandbox/28/execroot/harness_monorepo/bazel-out/darwin_arm64-fastbuild/bin/access-control/contracts/openapi/v1/AccessControlConsumerPactTest.runfiles/harness_monorepo/pacts
<http://localhost:60308/users/123>

Time: 0.957

OK (3 tests)

WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by com.google.testing.junit.runner.util.GoogleTestSecurityManager (file:/private/var/tmp/_bazel_imrankhan/b141c088e4409f9b6c4d0f13116258fa/external/remote_java_tools/java_tools/Runner_deploy.jar)
WARNING: Please consider reporting this to the maintainers of com.google.testing.junit.runner.util.GoogleTestSecurityManager
WARNING: System::setSecurityManager will be removed in a future release

BazelTestRunner exiting with a return value of 0
JVM shutdown hooks (if any) will run now.
The JVM will exit once they complete.

-- JVM shutdown starting at 2025-06-16 11:40:14 --

================================================================================
Target //access-control/contracts/openapi/v1:AccessControlConsumerPactTest up-to-date:
  /private/var/tmp/_bazel_imrankhan/b141c088e4409f9b6c4d0f13116258fa/execroot/harness_monorepo/bazel-out/darwin_arm64-fastbuild/bin/access-control/contracts/openapi/v1/AccessControlConsumerPactTest.jar
  /private/var/tmp/_bazel_imrankhan/b141c088e4409f9b6c4d0f13116258fa/execroot/harness_monorepo/bazel-out/darwin_arm64-fastbuild/bin/access-control/contracts/openapi/v1/AccessControlConsumerPactTest
INFO: Elapsed time: 3.016s, Critical Path: 2.82s
INFO: 2 processes: 1 internal, 1 darwin-sandbox.
INFO: Build completed successfully, 2 total actions
//access-control/contracts/openapi/v1:AccessControlConsumerPactTest      PASSED in 2.7s

Executed 1 out of 1 test: 1 test passes.

Hi, I'm trying to run tests for my provider following https://docs.pact.io/implementation_guides/jvm/provider/junit5spring I added the dependency

<dependency>
            <groupId>au.com.dius.pact.provider</groupId>
            <artifactId>junit5spring</artifactId>
            <version>4.6.10</version>
            <scope>test</scope>
        </dependency>

and started

mvn clean tests

I tried also with version 4.6.17 but still getting errors like

package au.com.dius.pact.provider.junit5spring does not exist
[ERROR] /Users/MY_PATH/ProviderContractVerificationTest.java:[8,2] cannot find symbol
[ERROR]   symbol: class Provider
[ERROR] /Users/MY_PATH/ProviderContractVerificationTest.java:[9,2] cannot find symbol
[ERROR]   symbol: class PactBroker
[ERROR] /Users/MY_PATH/ProviderContractVerificationTest.java:[15,17] cannot find symbol
[ERROR]   symbol:   class PactVerificationContext
[ERROR]   location: class ProviderContractVerificationTest
[ERROR] /Users/MY_PATH/ProviderContractVerificationTest.java:[21,39] cannot find symbol
[ERROR]   symbol:   class PactVerificationContext
[ERROR]   location: class ProviderContractVerificationTest
[ERROR] /Users/MY_PATH/ProviderContractVerificationTest.java:[7,13] cannot find symbol
[ERROR]   symbol: class SpringExtension
[ERROR] /Users/MY_PATH/ProviderContractVerificationTest.java:[20,17] cannot find symbol
[ERROR]   symbol:   class PactVerificationInvocationContextProvider
[ERROR]   location: class ProviderContractVerificationTest

I've also checked in my .m2 for the artifact

❯ ls ~/.m2/repository/au/com/dius/pact/provider/
4.6.10       4.6.17       junit5       junit5spring
❯ ls ~/.m2/repository/au/com/dius/pact/provider/junit5spring
4.6.10 4.6.17
❯ ls ~/.m2/repository/au/com/dius/pact/provider/junit5spring/4.6.10
_remote.repositories         junit5spring-4.6.10.jar      junit5spring-4.6.10.jar.sha1 junit5spring-4.6.10.pom      junit5spring-4.6.10.pom.sha1

I tried with both junit5 and junit5spring. Do you have any advices for that?

Hello guys 👋 I am interested if there is any chance to automatically set pacticipant repository-url in pactbroker. I know it can by done by

pact-broker create-or-update-pacticipant

cli. But since pacticipants are created automatically while publishing the pact is there any chance to pass the pacticipant repository-url info? We use maven plugin

au.com.dius.pact.provider:maven

./mvnw verify pact:publish \
  -DpactBrokerUrl="${{ inputs.PACT_BROKER_BASE_URL }}" \
  -Dpact.broker.user="${{ inputs.PACT_BROKER_USERNAME }}" \
  -Dpact.broker.password="${{ inputs.PACT_BROKER_PASSWORD }}" \

My provider project contains

service

dir with service code and unit tests in the root dir. Contract test (which generate pact file) is placed in

e2e-tests

directory directly under root. Can I also add provider verification tests in that dir or those need to be stored under

service > src > test

? I tried to create those tests in

e2e-tests

but when running I got an error

Caused by: org.springframework.context.ApplicationContextException: Unable to start reactive web server; nested exception is org.springframework.boot.web.context.MissingWebServerFactoryBeanException: No qualifying bean of type 'org.springframework.boot.web.reactive.server.ReactiveWebServerFactory' available: Unable to start AnnotationConfigReactiveWebServerApplicationContext due to missing ReactiveWebServerFactory bean

And I'm not sure if it's improper usage or it requires some additional configuration?

Hi, I'm using the pact gradle plugin https://plugins.gradle.org/plugin/au.com.dius.pact I have an issue with the canIDeploy task. I have a service that is both consumer and provider for APIs. I gave both internal service different names. For each pull request, both the consumer and provider tests are run. The canIDeploy task only takes one pacticipant and version. The issue is, that the canIDeploy task always verifies the latest version of the provider. Inside the PR, I just want to check whether the code state of the PR is consistent. Otherwise, another PR is creating an updated version and a race condition occurs where only the latest PR is green for canIDeploy. I think this should be solvable with specifying both services and versions together. The CLI seems to allow this, the plugin does not. Is there another way to prevent this race condition?

Hi team, I'm new to Pact and I'm trying to write my first consumer-side Pact-based tests. Could you point me to some resources(wikis, videos) that can help me get started? Thank you very much

This is a general question about matching, but applies to Pact-JVM. How do I specify/match an empty JSON array. We have a response that looks like:

{
  "destinations": [],
  "cities": [],
  "airports": [
    {
      "code": "MSY",
      "name": "Louis Armstrong New Orleans International Airport"
    }
  ]
}

I want to match that "destinations" and "cities" are indeed empty lists. I am trying to use

maxArrayLike("destinations", 0, example)

but I get an error on the Consumer test complaining that I either cannot leave that field empty, or that the example of 1 doesn't match the expected size of 0. Slack Conversation

Hi, we're using Pact Spring6/Springboot3 + JUnit5 Support for our Spring Pact Verification tests and our self hosted Pact broker uses a self signed certificate. To allow the tests to interact with the broker we're setting JVM system properties (

<http://javax.net|javax.net>.ssl.trustStore

and

<http://javax.net|javax.net>.ssl.trustStorePassword

) for the trust store and password. Is this the recommended approach for this or is there another better way we can configure the http client used to interact with the Pact broker?

Please see these instructions on running and accessing a Pact Broker over TLS https://docs.pact.io/pact_broker/advanced_topics/using-tls/

@Elson Ho has left the channel

Hi, my team has a library for reusing common code across our microservices. One of the modules is a http client for interacting with a service named

foo

. We have written consumer contract tests within this module, however, I’m not sure where to go from here. We could publish the pacts to the broker but that would just prevent the module from going out of sync with

foo

. We don’t record deployments of the module because it isn’t a service. So this wouldn’t help to prevent the services from going out of sync with

foo

. What we actually want to do is publish pacts for multiple services, services who happen to be using the module, to prevent them from going out of sync with the

foo

service. I’m not sure where we’re going wrong so any help would be greatly appreciated. Thanks 🙂

Hi Team, I have a couple of questions regarding the behavior and configuration of Work In Progress (WIP) pacts. 1. In a scenario where the WIP feature is enabled and a new contract is published to a WIP branch, but the provider hasn’t yet implemented the expected state or supported the feature, the provider pipeline won’t fail due to pending pacts being enabled. However, if the consumer pipeline includes a

can-i-deploy

step to check verification status—will this step fail, or still pass? 2. Also, according to the documentation, enabling WIP pacts initially seemed to require no changes on the provider side. However, I noticed that the

includeWipPactsSince

property is mentioned as part of the provider verification configuration to include modified pacts. Could someone clarify whether this property is mandatory for enabling WIP pacts on the consumer? Appreciate your insights!