Contract-Driven Testing in Banking: Realistic Mocks - Phil Royston

Contract-driven testing lets a tester work against a realistic mock instead of waiting for 50 integrated systems to behave, and that is what Phil Royston is bringing into a large bank. We talk about why mocks built on a developer's imagination produce unreliable tests, how agreed contract tests turn into mocks for API consumer and provider, and why the pitch to senior management fits on one slide while the middle managers hold the veto. Phil also explains why approved business requirements were not testable ones, what he means by parasitic end-to-end testing, and why his advice to any test manager is to wait for the crisis.