Pact Foundation

Hello,
Is there a way to test a consumer contract (as bi-directional contract) with a provider without publishing it to the broker ?

Yeah! The pact verifier cli has an option to pass it a contract file to verify

Which pact verifier cli are you using? (I am pretty sure they both have this option, the ruby one and the rust one)

but it seems the pact verifier cli is written with ruby

This is the one I'm using and it has a `-f` option for passing a pact file:

<https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_verifier_cli#command-line-interface>

Hmm, actually, I'm not sure if the ruby implementation of the pact verifier cli has this option. I'm not seeing it here: <https://github.com/pact-foundation/pact-provider-verifier#usage>

So looks like you'll want to try out the rust implementation (the first one I linked)

`--file` and `--dir` options are ignored when the env variable `PACT_BROKER_BASE_URL` is defined :confused:

also this tool verify pact files against a running provider.

is it possible to verify it with the provider pact submitted on the pact broker instead ?

yes, you don't need the pact broker if you're passing the contract file

yes, but it requires a running provider, is there a way to verify a consumer contract using the provider contract instead of a running provider ?

I think you're a little confused, the contract is written by the *consumer* and verified against a running instance of the *provider*. I'm not sure exactly what you mean by "provider contract" but the provider doesn't produce a contract

on my ci flow the provider publish an OAS on the pact broker.

I wanna know this is possible to verify if a consumer contract is compatible with my provider oas

(i'm trying to use bi-directional contracts)

I've never heard of bi-directional contracts in pact. I thought it only supported consumer-driven contracts

<https://docs.pactflow.io/docs/workshops/bi-directional-contract-testing>

&gt;  Is there a way to test a consumer contract (as bi-directional contract) with a provider without publishing it to the broker ?
Are you asking if there is a way to confirm locally if a change on the provider/consumer will break things, rather than finding out using `can-i-deploy` later in the pipeline? If so, not yet, but it’s on the <https://github.com/pactflow/roadmap/projects/1|roadmap> (see can-i-deploy local)

<@U021060919D> this is a Pactflow specific feature, and not something part of Pact OSS

I'm asking if I could run `can-i-deploy` command with a local contract instead of publishing it to the pact broker.

My ci/cd workflow is basically
`pact-broker publish`
`pact-broker can-i-deploy`
`pact-broker record-deployment`

and I would want to just run `can-i-deploy` locally (with uncommited local changes for example) to make sure my code is fine and only publish validated contracts

Yep that's exactly the feature we're building. Not ready yet but on the near term horizon as per that roadmap