# Am I understanding the Contract Testing the right way?

**URL:** <https://club.ministryoftesting.com/t/am-i-understanding-the-contract-testing-the-right-way/50978>\
**Category:** Discussions\
**Tags:** api-testing\
**Created:** [8 June 2021 08:47 UTC](https://club.ministryoftesting.com/t/am-i-understanding-the-contract-testing-the-right-way/50978 "2021-06-08T08:47:32Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![marie.drake](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/marie.drake/32/8015_2.png) [@marie.drake](https://club.ministryoftesting.com/u/marie.drake)\
**Post date:** [4 January 2022 14:58 UTC](https://club.ministryoftesting.com/t/am-i-understanding-the-contract-testing-the-right-way/50978/24 "2022-01-04T14:58:55Z")

</div>

I think Alexander has summed it up pretty well! But maybe to add a few more:

Pros:

- It can prevent data providers and/or consumers from deploying broken changes to production via Pact’s can-i-deploy tool
- It can serve as an additional source of truth and documentation for the team
- It eliminates the need of having a dedicated test environment with all the integrated services

Cons:

- Doesn’t work well with public APIs where the consumers are not known
- Only works best if the APIs are created in house. Doesn’t work well with third party APIs

---

_[View the full topic](https://club.ministryoftesting.com/t/am-i-understanding-the-contract-testing-the-right-way/50978)._