Skip to content

Code Review #116

Closed
Closed

Description

@mefellows

Problem

Customers that have manually written Pact tests, run the risk of missing test cases, over specifying consumer expectations or making any number of mistakes that may go unnoticed. As the code base evolves, this risk continues to grow unless the customer has very solid quality processes.

​With the introduction of PactFlow AI to generate test cases, we also run the risk of simply affirming what the code does, instead of applying pressure to the design of the solution.

Solution

The ideal solution to this problem is to provide a mechanism to automatically provide insights into their setup, actionable feedback and automatically update existing tests. The solution should also check to make sure that the tests challenge the system design instead of reaffirming the implementation.

Activity

  1. converted this from a draft issue on Jan 8, 2025
  2. added
    Q2Initiative is planned for a Q2 launch
    on Jan 8, 2025
  3. moved this from Planned (1-3 months) / Q4 2024 to Analysis (3-6 months) / Q1 2025 in Pactflow Roadmapon Jan 8, 2025
  4. moved this from Analysis (3-6 months) / Q2 2025 to Planned (1-3 months) / Q2 2025 in Pactflow Roadmapon Feb 27, 2025
  5. moved this from Planned (1-3 months) / Q2 2025 to Working on in Pactflow Roadmapon Apr 17, 2025
  6. YOU54F commented on Sep 26, 2025

    @YOU54F
    Member

    See https://docs.pactflow.io/docs/ai/using#reviewing-pact-tests for the AI Contract code review in initial beta

    We would hope to see this being richly integrated into users CI/CD systems, giving feedback and gating quality checks at review time, with contextual and actionable information

  7. mefellows commented on Sep 29, 2025

    @mefellows
    ContributorAuthor

    We've released code review support for Node/JS and Java. Based on real-world feedback and customer requests, we'll continue to add support for our other supported languages.

  8. moved this from Working on to Shipped 🚀 in Pactflow Roadmapon Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Q2Initiative is planned for a Q2 launch

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions