Test Environments are Expensive, Time-Consuming and Unreliable
When your application uses web services as backends, you are forced to test not only your own code but the configuration, data seeding, hardware capacity and support processes of each of those backends.
They cost hundreds of dollars a week.
They have to be reserved. And retained if your project is late.
They have to be seeded with matching accounts.
They go down in the middle of your testing.
They cannot handle the load.
They tend to have a wrong code version.
They are slow to troubleshoot.
Worst of all, you have to deal with these problems anew every release.
Mock the APIs, Save Time, Money and Sanity
The web services can be very complex, but their output is usually straightforward, and it can be mocked (a.k.a simulated, a.k.a. virtualized). Replace expensive, hard-to-reserve, unreliable and slow backend services with their mocked versions, and you can regain control over your project schedule and budget.
You don’t have to pay for each mock service separately.
You don’t have to ask for a lease from anyone.
You seed mock services from a spreadsheet, all services at once.
Mock services are never down, on maintenance or under deployment.
They can support the heavy load of your LT or PTE tests.
You don’t have to wait for backend’s code to become ready.
You own team can troubleshoot quickly.
Once you set mock services up, you can reuse them for many releases and projects.
Meet MockMotor: SOAP and REST, Data-Driven, Stateful, Scripted Mocks
There is just a tool to make it happen. MockMotor is built with a complex modern enterprise environment in mind, where the good ol’ SOAP services are intermixed with cool new REST ones, and Basic HTTP Auth is used side by side with OAuth and JWT.
It is all about the teamwork. Have as many members of your team using MockMotor as you like. The price will remain the same.
Multiple projects in works at once? Multiple overlapping releases? Isolate projects and releases to their own dedicated mock environments.
Need to mock one service or a thousand - one MockMotor installation supports them all — no need to break the bank.
Need to run multiple data-driven scenarios? Setting up a load test? MockMotor supports an unlimited number of mock accounts.
MockMotor can handle the heaviest enterprise load. The capacity scales with the available hardware.
Set up mock response times to mimic the real production services. Randomize response times or make them dependent on mock accounts’ properties.
Import thousands of mock accounts directly from Excel. Export to Excel and transfer them to another environment to seed a new project.
All your changes to mock responses are tracked and can be rolled back if required. Backup mock environments for later re-use.
Password-protected access. Environment-level access control. Only environment owners can change anything in the environment.
The number of calls per service. The number of errors. Detailed interaction log, including the payloads and headers.
You don’t have to throw your mocks away! Clone a mock environment or service, and you’re ready for your next release test cycle.
Forward requests to the real backends. Update mock accounts with reply data.
Update mock account values from a request and use them to control the response logic.
Test failure scenarios that are hard to reproduce in real systems.
Your test engineers are probably not experts in web services. That’s OK. The UI is simple and full of tips.
Served Millions of Mocked Responses and Counting
Some MockMotor instances have just a couple of small services called a few times a day, and some have dozens of environments, hundreds of services and hundreds of thousands of mock accounts with test runs sending production-like volumes.