Another question, now that my consumer tests for the workshop are updated, I want to upgrade the provider side, too. I've got a simple Spring service there that I'd like to reuse, so I've upgraded my dependencies to:

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

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

and I'm following the example here: https://docs.pact.io/implementation_guides/jvm/provider/junit5spring However, I'm probably missing one or more dependencies here:

@ExtendWith(SpringExtension.class)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@Provider("address_provider")
@PactFolder("src/test/pacts")
public class ContractTest {

    @TestTemplate
    @ExtendWith(PactVerificationSpringProvider.class)
    public void pactVerificationTestTemplate(PactVerificationContext context) {
        context.verifyInteraction();
    }
}

as it can't find the

@Provider

,

PactVerificationSpringProvider

and

PactVerificationContext

classes. Again, probably something pretty obvious but I've been stuck on this for a while now. I know that page references Pact v 4.4.x so that might be the problem but I'd really like to use the latest versions.

Any chance you could help Bas @uglyog?

No idea, those classes and annotations haven't changed. 4.6.2 requires min JDK 17, so check that you have that.

How are you running it Bas - command line? Mind sharing the logs/console?

There's not a lot to run as the code doesn't compile 🙂 I've now 'downgraded' (or rather upgraded less) to

4.4.6

and that resolves these issues. I am running on Java 17, by the way.

Try changing this line as well: https://github.com/basdijkstra/introduction-to-contract-testing/blob/upgrade_to_latest_pact_version/address-provider/pom.xml#L24

To what, exactly? 4.0.10 seems to be the latest version

Hi Bas, I’ll see if we can take a look tomorrow. Hopefully something simple!

Just having a look now, on a mac m1, openjdk 17 and maven both installed via homebrew. managed to run all the tests out the box, and then upgraded to 4.6.2 on the provider and that passed too. Just added some local ci runs to replicate and then will push up a fork.

Cheers Saf! Really curious to see what I’ve done wrong, the only thing I haven’t tried is completely wiping and repopulating my local Maven repo.

I just dropped into the repo, updated the pom.xml and did a

mvn test

again. Just did a

mvn clean

and then

mvn test

just incase it didn’t rebuild after changing the pom

Thanks! I’ll check first thing tomorrow morning as I CBA to fire up my laptop again tonight

also just tested against a docker image.

maven:3-eclipse-temurin-17

linux arm and amd64. I’ll just up some repros so you can have a nose tomorrow. enjoy the feet up 👍

I’m on Windows so that might just be a factor here too 😆

See what happens https://github.com/YOU54F/introduction-to-contract-testing/actions/runs/6028097174 fingerscrossed Got a windows runner here changes https://github.com/basdijkstra/introduction-to-contract-testing/compare/main...YOU54F:introduction-to-contract-testing:ci

Legend! Again, I’ll check this out first thing tomorrow morning

Exactly the same problem here, @Bas Dijkstra what did you do to fix? Thank you

@Jorge Casto Núñez de Castro Cobo I’m still using Pact 4.4.x for the provider. Not the solution I prefer but as it’s for a workshop I’m running in just over a week it’ll do.

oh... 😔