A collection of 9 posts
Hypermedia based APIs are becoming much more prevalent as the format used for web application APIs. We use HAL for our APIs here at Pactflow, and the Pact Broker has been using HAL
7 min read
How to implement a schema-based contract testing strategy with Pactflow using JSON Schemas, and a look into using Open API (Swagger) with Pact and Pactflow
4 min read
A deep dive into schemas and specifications, how can they be used for schema-based contract testing and their respective benefits and tradeoffs
8 min read
I want to do a deep dive into the experience of one particular company that ended up removing their Pact tests because of the pain they were causing - I hope it will help others to avoid the same pain.
5 min read
Learn how to make Pact + Cypress work together to create a repeatable, reliable UI test suite that won't result in production issues.
How does pact differ to Postman? Postman is a functional API testing tool whereas Pact is a contract testing tool. Pact provides guarantees that your systems are compatible with one another using fast, isolated and reliable tests. Learn more about these differences in this article.
While Pact has successfully helped many organisations, there are also organisations that have had problems with their Pact implementations. Let's go through some of the reasons why Pact implementations fail to deliver on their promised benefits, and how you can avoid these pitfalls.
Ensuring that all our applications still work after each deployment can seem like a daunting task that only an extensive set of end-to-end tests can achieve. However, this can stop us achieving the goal that we hoped to achieve by using microservices in the first place - shipping code fast.
3 min read
Introducing verification results, our drill-down view into Pact verification failures at the interaction level.