-
# Description
Implement a method for creating stubs in Cypress tests based on contracts generated from Pact.
## Acceptance Criteria
- [ ] TBD
U-DON updated
2 years ago
-
I don't see any reference in `README.md` on how to set up `pactman` on the Consumer side to publish a new contract to Pact Broker instead store it locally inside the repo.
Can someone point me, to …
-
## Context
We are currently undergoing a large scale project of adding contract testing to components being run on embedded devices. As embedded device components they are written in either C++ or …
-
Which of the contracts is the latest (looking at https://github.com/kadena-io/chainweb-node/tree/master/pact/namespaces)?
Maybe a README could be added?
-
Can I split Message Contracts Verification methods into different Test Classes? Currently I have 2 Consumers with 1 Interaction each and 1 Provider that needs to verify those 2 Contracts. In the Provi…
-
### Feature Description
We (my team and I) are looking for a Contract Testing lib/framework for Axon Framework based services. Something similar to Pact or Spring Cloud Contract.
But at the mome…
-
The pact-stub-server has a `--provider-state-header-name` that allows for selecting a better matching interaction based on a header containing the requested provider state. The pact-verifier-cli (rust…
-
The gradlew pactVerify command does not verify contracts with following setup.
Gradle version -5.2.1
"au.com.dius.pact" version "4.1.0"
The provider returns asynchronus message (it returns messages…
-
Being able to configure metadata matching at one or more levels deep and ignoring additional keys would also help us configure the metadata in contracts how we want to.
Ref: https://pact-foundation…
-
Hello,
Today I use pact to verify all my contracts when there is a pull request,
I'm using the same branch name for the consumer/provider as suggested in the documentation.
The problem is that if…