“- Proxies requests to a live upstream.”
“- Records actual request/response interactions.”
“- Generates reusable JSON stub mappings.”
“- Supports filtering, header capture, body matching, and snapshotting.”
“- Can immediately serve recorded stubs instead of the live backend.”
“Particularly good for CI pipelines and developer environments.”
“- Choose WireMock if you want mature request matching, editable JSON fixtures, rich configuration, and a well-established testing ecosystem.”
“- Runs as an HTTP(S) proxy.”
“- Captures real requests and responses.”
“- Exports recordings as JSON expectations or Java code.”
“- Supports promoting recordings into active mocks.”
“- Offers consolidation, parameterization, and credential redaction.”
“Particularly attractive if you want to automate the entire recording-to-mocking process.”
“- Choose MockServer if your priority is capturing real traffic and automatically turning it into reusable mocks with minimal manual intervention.”
“- Captures traffic through a proxy.”
“- Saves interactions as simulation files.”
“- Switches between capture and simulation modes.”
“- Supports spying, where unmatched requests still reach the real backend.”
“- Useful for service virtualization and integration testing.”
“A particularly natural fit if you want a dedicated record-and-replay workflow.”
“- Choose Hoverfly if you prefer explicit capture, spy, and simulate modes with portable simulation artifacts.”