Part 3 Provider-driven contract testing

While consumer-driven contract testing (CDCT) remains the most popular approach, it might not suit how your teams work. PactFlow introduced the concept of provider-driven contract testing (PDCT) or bi-directional contract testing to address the limitations of CDCT. With this knowledge, you can use existing tests and generate contracts from them.

This part of the book explores the concept of PDCT in more detail. Chapter 11 delves into the theory behind PDCT, why it was introduced, and how it’s different from CDCT. You also learn how to implement popular contract test adapters such as Cypress consumer adapter, WireMock consumer adapter, Postman provider adapter, and Dredd provider adapter. Finally, chapter 12 looks at converting your existing integration or end-to-end tests into contract tests. By the end of this section of the book, you’ll have gained confidence in implementing PDCT in your work projects if this approach suits your team better.