Code Review

[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.

[YOU54F]

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

[mefellows]

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.