Update Pact to 4.7.6 and manage its version in the parent pom

Open Beginner friendly
#147 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
java, spring-boot
Domain
testing-qa

Research direction

The Pact version is pinned in the three module poms (account-service, customer-service, order-service) at 4.6.20, so start by finding those dependency entries and the parent pom.xml. Introduce a pact.version property in the parent, point the modules at it, and bump to 4.7.6. Done when the contract tests run green with the new version; the payload does not name the test classes, so locate them in each module.

Written by the indexing model from the issue text.

Description

enhancement

Problem

au.com.dius.pact.provider:junit5spring (account-service) and au.com.dius.pact.consumer:junit5 (customer-service, order-service) use version 4.6.20; the latest release is 4.7.6. The version is duplicated in three module poms.

Suggested solution

  • Bump Pact to 4.7.6.
  • Introduce a pact.version property (or dependencyManagement entry) in the parent pom.xml and use it in all modules.
  • Re-run the contract tests after the upgrade (see the Pact issues).
Dominant language
Java
Stars
12
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piomin/sample-spring-cloud-testing

All issues in piomin/sample-spring-cloud-testing

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.