Contract-Driven Testing in Banking: Realistic Mocks - Phil Royston
From Software Testing Unleashed - QA, DevEx & Quality Engineering · 30:14
Show by Richard Seidl | Software Development & Testing Expert
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.
More episodes of Software Testing Unleashed - QA, DevEx & Quality Engineering
More episodes
- GenAI Evaluation: One Model, Three Goals - Deepshikha, Anamika Mukhopadhyay
- Building Trust in Teams: Start Small - Michael Kutz, Linda Van De Vooren
- Mental Skills: Testers Can't Outsource Their Brain to AI - Ard Kramer
- Testing AI Models as Magic Boxes: Why Checks Fail - Michael Bolton
- Dark Side of Testing: The Failures We Cause Ourselves - Bart Knaack
- Quality Hunting: Testing for Information Instead of Bugs - Rik Marselis
- On-Site Testing Conferences: Why Networking Needs Presence - Okan Çakmak
- You Need a Test Automation Strategy Before AI - Michaël Pilaeten
- Agentic Systems in Testing: Why Humans Stay in the Loop - Nishan Portoyan
- Welcome to Software Testing Unleashed
PodSearch is a free, independent podcast search engine. Read about PodSearch, the privacy policy or contact us.