Service Virtualization: Path from Decision to Execution
summary
Compares concrete tools and tradeoffs: mountebank (contract-driven, lightweight, no recorder), hoverfly (record-and-playback, CLI/Docker/Kubernetes, HTTP-only), CA/Broadcom (enterprise, many protocols, monolithic, heavy consulting) and SmartBear ServiceRepro (codeless UI, on‑prem hub, easier rollout). Recommends record-and-playback where possible, integrate virtual services into CI/CD, virtualize only the layers needed, and measure impact by defects found, cross-team collaboration and time-to-release — a cited case saves nearly $500k on training environments.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:00About SmartBear
- 2:00Agenda
- 2:43Mocking vs Virtualization
- 3:41Why Virtualization
- 7:20Selecting a Suitable Tool
- 7:55Criteria to Consider
- 11:30Tool Examples
- 13:39Mountebank
- 15:52Hoverfly
- 18:46CA Technologies
- 23:46Best Practices
- 26:22What to Virtualize
- 28:46Use Cases
- 30:57Measuring Impact
- 34:57Questions
related talks
27mTesting Cloud Apps: Mocks vs. Service Virtualization vs. Remocal Tools
43mService Virtualized HTTP - Make Your Tests Resilient with Servirtium
40mDeploy and Destroy Complete Test Environments
42mMicroservice Testing Techniques
36mService Virtualisation and AI for Shift-Left Testing
53mChange your tools, change your outcome
54mUnraveling the Differences
09mSmartBear Software