Mock Server for API Load Testing

... We've saved weeks and $$$ in LT by using mocks instead of PROD-like backends.


On-Premises: Stable Response Time
Horizontally Scalable: Higher Loads
SOAP, REST, GraphQL & Websockets
Data-Driven: 1000s of Mock Accounts
Team-Oriented: Multi-User, AD/LDAP Integration, Change History
Standalone: No Dependencies

 Linux  Windows

Why Use Mocks in Load Tests?

Why not use the real test APIs?

Because Real Test APIs …

Unstable and Prone to go Down
Can't Handle the Load
Their Response Time Jitters
Cost a Lot. Sometimes helluvalot!
Have to be Reserved, All at Once
Have to be Seeded, Consistently to Each Other
Painfully Slow to Troubleshoot
Their Setup is not Preserved for Next Release

How Big is the ROI?

Modern applications rely on tens and hundreds of external APIs.

Using MockMotor to simulate them, a project can realize THOUSANDS of DOLLARS in monthly savings.

Lower Operational Expenses

Test APIs capable of load testing cost thousands of dollars a month. A project can save most of that cost per backend API, even taking into account the switch costs.

Lower Losses due to Downtimes

Even the best test APIs rarely have availability over 0.99. If a project uses ten such APIs, the forced downtime can reach 10%.

More Testing Capabilities, for Free

Outage and graceful degradation testing are costly to setup with real APIs. These capabilities come as a part of the standard package with mock services.

Fewer False Positives

The response times of mocks are less prone to misconfiguration and environmental issues. The test runs are more predictable, with fewer unnecessary re-runs.

The savings grow when MockMotor is used across multiple releases and projects.

Served Millions of Mocked Responses and Counting