Service Virtualisation and AI for Shift-Left Testing
summary
Argues that shifting tests left cuts defect cost and shows a concrete pipeline: use OpenAPI specs to generate service stubs and API tests, run hundreds of regression API tests in ~3 minutes, and keep UI testing minimal. Demonstrates a small toolchain—Hoverfly for stubs, Karate for API automation, and a homegrown Atlas that generates stubs and test scripts from API specs—claims it largely works but requires human validation for AI-generated tests and careful data/schema handling.
AI-written summary · about
chapters (8)
- 0:00Shift-left testing intro
- 1:33Why shift-left matters
- 6:30Collaboration and automation
- 11:51Overcoming testing dependencies
- 17:57API testing strategy
- 22:17API spec-driven dev
- 30:11UI automation challenges
- 35:27Conclusion & Q&A
related talks
25mRethinking Software Quality: Why API Testing Needs to Change
23mSolving Challenges in API Testing to Achieve More Agile Development
47mNext generation of API testing : Unleashing the power of AI
54mShould You Be Doing More API Testing?
01h 28mShift-Left Testing
40mFrom Bugs to Brilliance: Leveraging AI in Modern Software Testing
26mMocking and Deploying an AI Chatbot in Minutes
42mThe Power of Human and AI Collaboration in Software Testing