Contract Testing and Laravel: Reliability in APIs Between Microservices
summary
Explains using contract testing (with Pact) to verify only interservice API communication and catch integration breaks before production. Describes using Pact’s mock server and Pact Broker to publish/version JSON contracts, plus Laravel tools Salon and Spectator and OpenAPI validation; demonstrates runnable consumer and provider tests in two GitLab Laravel repositories that generate pacts and record verification results, yielding faster isolated tests, independent deploys, automatic documentation, and a concrete Pact workflow.
AI-written summary · about
chapters (9)
- 0:00Contract testing intro
- 4:01Contract testing definition
- 7:54Salon & Spectator for Laravel APIs
- 12:32Spectator limits vs contract testing
- 17:07Pact and Pact Broker
- 23:55Pact pros and cons
- 30:21Laravel-Pact Broker workflow
- 32:09Solutions with vs without Pact
- 33:36Resources
related talks
46mPractical Contract Testing with Pact in PHP
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
09m"Contract Testing 101"
23mContract Testing for Mobile Application Development
39mWhy you should contract test your Microservices 🧭
24mHow to test microservices and stay sane
39mPacts to the Rescue! Making your microservices play nicely together
22mContract Testing – An efficient way for integration testing