Comparison of API simulation tools
 | This article needs additional citations for verification. |
 | This article, Comparison of API simulation tools, has recently been created via the Articles for creation process. Please check to see if the reviewer has accidentally left this template after accepting the draft and take appropriate action as necessary.
Reviewer tools: Inform author |
The tools listed here support simulating APIs. They are also called[1] API mocking tools, service virtualization tools and over the wire test doubles.
| FOSS | Free | Supported protocols and APIs | Has a GUI | Scriptable/Programmable | Docker support | Cloud offering | Quick start | |
|---|---|---|---|---|---|---|---|---|
| Charles Proxy | No; Proprietary | No | HTTP(S) | Yes | No | No | No | |
| Hoverfly | Yes; Apache 2[2] | Yes | HTTP(S) | No | Yes | Yes | Yes [3] | Hoverfly introduction |
| Mountebank | Yes; MIT[4] | Yes | HTTP(S) TCP SMTP[5] |
No | Yes[6] | Yes[7] | No | Mountebank Getting Started |
| SoapUI MockServer | Yes; EUPL[8] | Yes | HTTP(S)[9] | Yes[9] | No[9] | No[9] | No[9] | MockServer quick start |
| Traffic Parrot | No; Proprietary[10] | Yes (Community Edition)[10] | HTTP(S) JMS IBM® MQ (in beta)[10] |
Yes[10] | Yes[11] | Yes[10] | No | Traffic Parrot Quick Start |
| Wiremock | Yes; Apache 2 | Yes | HTTP(S) | No | Yes | Yes | Yes [12] | Wiremock Getting Started |
References
- ^ Tom Akehurst at the Next Gen Service Virtualisation Forum
- ^ Hoverfly license
- ^ Hoverfly Cloud
- ^ Mountebank license
- ^ Moutebank home page
- ^ Moutebank injection
- ^ Running Moutebank in Docker
- ^ SoapUI Licence
- ^ a b c d e SoapUI MockServer documentation
- ^ a b c d e Traffic Parrot home page
- ^ Traffic Parrot Extensions Documentation
- ^ Mocklab