Contract Testing for Mobile Application Development
summary
Claims that contract testing runs early and in isolation to catch integration breaks before backend deploys and replaces slow flaky end-to-end tests, delivers concrete steps: create consumer-driven contracts, run consumer tests against a mock service, verify provider behavior for a defined provider state, expect specific HTTP status headers and JSON body, then push contracts to a Pact broker and have providers pull and run verification. Tooling examples: pact and Spring Cloud Contract, plus the testComplete/to verify push‑and‑pull workflow.
AI-written summary · about
chapters (12)
- 0:00Contract testing intro
- 1:05Mobile testing process
- 2:10Contract testing at integration
- 6:25What is contract testing
- 10:44Contract testing tools
- 11:04Monolith vs microservices
- 13:51Dog App example
- 18:55Pact contracts
- 20:47Q&A: WebSockets & queues
- 21:31Q&A: Tools needed
- 22:12Q&A: Versioning maintainability
- 23:14Closing summary
related talks
22mContract Testing – An efficient way for integration testing
09m"Contract Testing 101"
42mWhat Contract Tests Are
32mConsumer-Driven Contract: A better approach for API Testing
39mWhy you should contract test your Microservices 🧭
47mContract-Based Testing for Microservices and UI
01h 13mContract Testing Made Easy: Master Pact for Microservices in C#
24mHow to test microservices and stay sane