From Contracts to Confidence: Spring Cloud Contract 5 in the Age of AI
summary
Spring Cloud Contract 5 removes decades-old cruft: it upgrades to WireMock 3 and drops the custom WireMock integration, deletes the shaded jar approach, renames stub properties to Spring Cloud Contract stub runner, and migrates Gradle to a contract test source set while removing Jakarta inject support. A Groovy JSON→JSONPath converter is rewritten to Java (AI-assisted) enabling an optional strict JSON assertions mode. A new project Stubborn ships a broker, dashboard, proxy that captures HTTP/Kafka traffic, publishes contracts, and runs verifications — demo is live and working.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:32Spring Cloud Contract 5 release
- 9:45Spring Cloud Contract 5.1 features
- 12:17How contract testing works
- 15:25Why contract testing matters
- 19:21Future improvements
- 24:02AI and contract testing
- 33:33AI agents and specs
- 34:56Introducing Stubborn
- 45:34AI-driven contract tests
- 45:54Q&A
related talks
30mManaging APIs and Contracts in a Microservices World Using Spring Cloud Contract
45mREST and Messaging contracts with Spring Cloud Contract
33mPractical Contract Testing with Spring Cloud Contract
01h 04mConsumer Driven Contracts and Your Microservice Architecture
01h 11mBootiful Testing
52mBootiful Testing
44mBuild Resilient Systems with Spring Cloud Contract and Testcontainers
42mInvestigating Contract Testing