Service Virtualized HTTP - Make Your Tests Resilient with Servirtium
summary
Servirtium records real HTTP interactions as record/playback Markdown recordings stored in source control and runs as a man-in-the-middle HTTP proxy or in-process library for Java, Kotlin, .NET, Node, Rust and others. Tests integrate with JUnit/TestNG and switch between direct, record and playback modes; a Selenium demo shrinks a 45s remote run to 3s on playback. A periodic re-record job diffs markdown to flag contract drift, and hand-edited recordings allow development before a dependent service exists.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:54Mocking (SV recap) In-process mocking that is for the programming language in question
- 8:25Should we share services in development? dev workstation
- 13:48How do we get those mock interactions? test can switch between record
- 26:04Record vs Playback Record Mode
- 30:33Different versions of Servirtium
- 31:15Key concept - re-record & fail a build if different
related talks
38mService Virtualization: Path from Decision to Execution
27mEffectively Testing Services
46mRecord-Replay API Test Cases & Data Mocks without writing code
09mSmartBear Software
42mMicroservice Testing Techniques
02h 36mTesting Java Microservice
36mAPI Testing Without Writing Test Cases and Mocks
27mTesting Cloud Apps: Mocks vs. Service Virtualization vs. Remocal Tools