Hi.
I'm trying to determine if pactflow, or any other pre-existing solution, allows for bi-directional contract testing of message based / event driven system. Is anyone aware of a solution along those lines?
i.e. Similar to the bi-directional contract testing feature pactflow supports where the provider publishes an Open API spec doc, I'm looking for a solution where the components which produce the messages/events would be able to upload a contract file of what it does produce to the broker and then both consumer and producer CICD pipelines be able to use a simple 'can-i-deploy' like call to the broker which will compare the consumer and producer contract files for compatibility.
m
Matt (pactflow.io / pact-js / pact-go)
08/19/2024, 4:07 AM
Hi Ryan,
We don’t have a solution for this at this moment I’m afraid.
For now, the only option I’m aware of that would be compatible with the
can-i-deploy
workflow would be to use the standard consumer-driven testing event based testing (so-called “message pact”) with Pact