-
### Checklist
- [x] I have searched for existing issues for issues like this one. The issue has not been posted.
- [x] I have provided reproducible steps. (No "as the title says" posts please. *…
-
Previous Pact Specification versions all follow `A.B.C` format, even if both `B` and `C` were just `0`. `4.0` specification breaks this. Now I recognize that a semantic version parser should be able t…
-
Warning: Calling bottle :unneeded is deprecated! There is no replacement.
Please report this issue to the kadena-io/pact tap (not Homebrew/brew or Homebrew/core):
/usr/local/Homebrew/Library/Taps/…
-
As per the documentation and https://github.com/DiUS/pact-jvm/issues/403 / https://github.com/DiUS/pact-jvm/issues/459 , I understand that once the consumer-contact testing is over we could publish a…
-
:\pact-workshop-js-master>npm run test:pact:provider
> pact-workshop-js@1.0.0 test:pact:provider C:\pact-workshop-js-master
> mocha --timeout 1000000 provider/test/providerPact.spec.js
…
-
Has anyone considered developing a test suite that you could run against a pact implementation? Similar to https://github.com/ruby/spec, it could be used to verify an implementation conforms to the sp…
-
By default configuration is stored at `~/.config/pact/pact.json`. Ideally if the current directory contains a `pact.json` that file should be loaded with precedence.
-
I'm using `pact-python` version 1.7.0.
There doesn't seem to be a way to verify with a specific pact by passing in a pact URL.
I tried passing a `pact_url` kwarg into `MessageProvider.verify_with_…
-
The `@PactBroker` annotation allows me to either hard-code tags, or provide them using a system property. The system property lets me specify different tags at runtime, which is great for doing things…
-
Hello all, I'm having an issue that I want to share with you.
**The scenario:**
The development team had to add more fields to existing endpoints of an API, but because this breaks the contract be…