| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Original HTTPS Page] |
Our new feature, Bi-Directional Contract Testing is a type of static contract testing where two contracts—one representing the consumer expectations, and another representing the provider capability—are compared to ensure they are compatible.
With this new feature you can choose:
Read the documentation for an overview or dive right into one of the supported adapters.
If you’re looking for something more hands-on, watch one of the demos below.
Videos
Fast, easy and reliable testing for integrating web apps, APIs and microservices
Testing microservices shouldn't involve setting up complex end-to-end test environments, creating lengthy integration suites and managing test data. Stop wasting time, and start releasing.
Create MSW (mock-service-worker) mocks, and generate pact contracts from the recorded interactions.
Demonstrate running a consumer pact test with Cypress
An example of a consumer that uses Pact+PactFlow to create a consumer driven contract with its provider
Terraform provider for Pact Broker (and Pactflow)
An example of a provider that uses Pact+PactFlow to honour a consumer driven contract with its consumer
Bi-Directional Contract Testing example consumer using a BYO testing tool (Playwright) to generate Pact consumer contracts
Bi-Directional Contract Testing example provider using a SoapUI as the API functional test tool
Example provider using ReadyAPI tests generated from an OAS and PactFlow's bi-directional contracts feature
Bi-Directional Contract Testing example consumer using a BYO testing tool (Nock) to generate Pact consumer contracts
Cypress bi-directional contract testing example project
Example Java GraphQL consumer
Loading…
Loading…
| Back | FazBrowse Home | New Git URL |