Using OpenAPI Documentation in Contract Testing with Pactflow

Get more of your team involved and maintain traction to ensure a successful rollout of your contract testing initiative using OpenAPI Documentation.

Using the consumer driven Pact contract testing framework gives development teams the confidence to deploy more often, move faster and save time and money maintaining E2E test suites. While the outcomes are great, in some instances, contract testing initiatives can fall to the wayside or be hindered to expand further than one team or an initial PoC.

With the recent launch of our new feature—Bi-Directional Contract Testing—you now have more opportunities to expand your contract testing initiative where the consumer driven framework may not be appropriate or you’ve felt some friction.

Have you heard the following objections?
“We already have tests in place, why do we need to write Pact tests too?”
“We have a legacy application and it’s too difficult to unit test”
“Consumer driven contract testing is too hard”
“We have OpenAPI documents for our APIs - why do we still have breaking changes?”

If so, watch this recording of a live webinar to learn how you can now use OpenAPI in your contract testing strategy, and leverage your investment in existing tools such as Cypress and Postman.

In this session, designed specifically for developers, our team will show you how to use and get the most out of Bi-Directional Contract Testing and answer any questions you may have.

What we will cover:
- Common blockers to starting and scaling contract testing
- How Bi-Directional Contract Testing helps solve them
- A demonstration of how to use OpenAPI alongside Cypress and Postman in a contract testing workflow
- How Pactflow’s unified contract testing platform enables you to choose between consumer-driven and API first approach

Resources:

In-browser Katacoda tutorial - interactive and very easy to start with 🥳
Mix & match Bi-Directional Consumer & Providers

✍️ View the examples used in the demo:

- Create or log in to your GitHubResources

[keving]

If we don't have Postman tests but we do have a swagger file can we upload that and would it still work ? If yes, could you document that ?

[MuratKeremOzcan]

I like this. We can just use Cypress instead of Newman as well.

[PrzemysawSech]

Love BYO, I see a usage when there's no control over 3rd party pipeline.