Bi-Directional Contract Testing Workshop

To use OpenAPI as part of a contract testing strategy

API testing tools such as Dredd or Postman can be used with API Hub for Contract Testing

To publish contracts (such as a pact file or an OpenAPI document) to API Hub for Contract Testing

To prevent deploying breaking changes to an environment, such as production

To use existing mocking tools (such as Mountebank or Wiremock) to create a consumer contract

See our online katacoda tutorials. The specific bi-directional course that covers the below agenda can be found here.

You can pick and choose a bi-directional consumer/provider example from our exhaustive list, and you will start by forking the repositories into your own Github account, setting up Github Actions as CI builds, and configuring the projects to point to your own API Hub for Contract Testing account. Don't worry, we will take you step by step in the workshop.

Create and document an API using OpenAPI Specification

Write tests for the API using an API testing tool such as RestAssured, Dredd, Postman ,and Schemathesis/Swashbuckle

Publish the provider contract (an OpenAPI document) to API Hub for Contract Testing

Deploy the provider to production

Write the API consumer

Write tests for an API client using tools such as Mountebank, Nock, Wiremock, Nock, Cypress, and Mock-Service-Worker or traditional Pact .NET to mock the API, and convert those mocks into a consumer contract

Publish the consumer contract to API Hub for Contract Testing

Deploy the consumer to production

Learn about API Hub for Contract Testing's breaking change detection system