Each page below maps one tool's concepts onto Traffic Parrot's, shows one mock written both ways, and says where each tool's scope ends. Pick the tool you use today.
| Tool | What it is | What carries over to Traffic Parrot | Page |
|---|---|---|---|
| Hoverfly | A mock and proxy server whose Modify and Synthesize middleware hands each request and response to an executable as JSON on stdin and reads the result back from stdout. | The out-of-process middleware idea: Traffic Parrot's external-process response transformer sends the matched request and the response to your executable's stdin and applies the mutated response it reads back from stdout. | Hoverfly middleware in Traffic Parrot |
| Mockoon | A desktop application, with a command-line runner and a Docker image for headless use, that mocks HTTP, HTTPS and WebSocket on one developer's machine. | A route with a method, a path and a response, rules that pick a response from the request, a templated body and a proxy for what is not mocked yet each have a direct counterpart in the mapping editor; the environment file is translated route by route. | Traffic Parrot for Mockoon users |
| MockServer | A mock and proxy server that holds expectations, each a request matcher paired with a response action, put there by a client library, the REST API, an initializer file or its dashboard. | The model: a mapping is a request matcher paired with a response, with a priority, scenario state, delays, faults and a request journal, so an expectation reads like a mapping with the field names changed and is translated expectation by expectation. | Traffic Parrot for MockServer users |
| Mountebank | A Node.js server whose imposters, one port and one protocol each, hold stubs described as JSON and driven through an HTTP administration API; its built-in protocols are HTTP, HTTPS, TCP and SMTP. | The way of working: a test double that is a separate process speaking the real protocol, described as JSON, driven from any language over an HTTP API and able to record a real service; the imposter files are translated stub by stub. | Traffic Parrot for Mountebank users |
| WireMock | An HTTP mock server, embedded in a test process as a library or run standalone, whose stubs are JSON mappings with response bodies kept in a __files directory. | Everything: Traffic Parrot embeds a fork of WireMock, so your JSON mappings and __files load and serve unchanged, and a WireMock ZIP archive imports directly. | Traffic Parrot for WireMock users |