Contract Testing – An efficient way for integration testing
summary
Argues that contract testing replaces many fragile integration tests by validating the actual agreement between caller and endpoint and runs locally without deployed infra or generic test accounts; demonstrates both consumer-driven and provider-driven approaches, a working CI pipeline integration used with PactNet, and a real client deployment where a generalized pipeline under 100 lines enforces team collaboration; claims faster, more stable tests, easier debugging, and successful use in microservice integration scenarios.
AI-written summary · about
chapters (12)
- 0:00Contract testing intro
- 1:14Traditional integration testing problems
- 3:45Contract testing management
- 4:49How contract testing works
- 6:13Types of contract testing
- 8:19Consumer vs provider driven
- 9:21Key benefits of contract testing
- 11:10Use cases for contract testing
- 12:32Technologies for contract testing
- 13:54Pipeline integration
- 15:40Summary
- 16:21Q&A
related talks
23mContract Testing for Mobile Application Development
09m"Contract Testing 101"
39mWhy you should contract test your Microservices 🧭
42mWhat Contract Tests Are
32mConsumer-Driven Contract: A better approach for API Testing
47mContract-Based Testing for Microservices and UI
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
42mNonviolent Communication in the world of distributed systems