Related Tech

Mockaton wins overall, but it’s worth knowing the strengths of related tools. For instance, start with Burp, Charles Proxy, and JSON Server. Also, if you use StoryBook for testing non-core components, learn about MSW (you can map MSW to the Mockaton file structure, so you can get the benefits of both).

Proxy-like

These are similar to Mockaton in the sense that you can modify the mock response without losing or risking your frontend code state. For example, if you are polling, and you want to test the state change.

• Chrome DevTools allows for overriding responses.
• Reverse Proxies such as Burp are also handy for overriding responses. Not easy but very powerful.
• mimtproxy
• HTTP Toolkit
• Proxyman
• Charles Proxy

Server Side

• Wire Mock
• Fiddler
• JSON Server
• Swagger
• Mockoon
• Mock

Client Side (Service Worker)

In contrast to Mockaton, which is an HTTP Server, these programs intercept your browser’s requests (or Node’s). Since they use a Service Worker, by design, they inherit their limitations.

• MSW
• Nock
• Fetch Mock
• Mentoss
• MirageJS