Hi! In a provider test, what could be the reason u...
# pact-js
t
Hi! In a provider test, what could be the reason using
mainBranch: true
triggers an error (No pacts found matching the given consumer version selectors in pact broker xxx), and
latest: true
doesn't? The consumer publishes contracts in feature branches as well as in
main
; we've also confirmed the participant's details
Main Branch: main
thank you
using
mainBranch:true
in conjunction of
deployed: true
seems to work in some cases: • ConsA <> ProvA: • ConsA <> ProvB:
m
The main branch is for selecting contracts that match the _consumer_’s main branch. If a consumer hasn’t published a contract for its main branch, that would likely be the reason
t
the weird thing is that the consumer is publishing contracts to the main branch... Could this also be related to marking contracts are deployed/released or not? I've deleted all the contracts and restarted from scratch, I'll check within the next couple of days as PRs get pushed from all services.
👍 1
m
If you set logs to verbose, we should be able to see the calls to the broker and why it isn’t finding anything
👍 1