Decouple Your Projects from External Test APIs
<img src="/pm/images/2527Thumbnail.png" width=“100%” srcset="/pm/images/2527Thumbnail_huc91c0ceff46359598832c43766bcdd0f_366382_100x0_resize_q75_box_3.png 200w, /pm/images/2527Thumbnail_huc91c0ceff46359598832c43766bcdd0f_366382_200x0_resize_q75_box_3.png 400w, /pm/images/2527Thumbnail_huc91c0ceff46359598832c43766bcdd0f_366382_400x0_resize_q75_box_3.png 800w, /pm/images/2527Thumbnail_huc91c0ceff46359598832c43766bcdd0f_366382_800x0_resize_q75_box_3.png 1600w, /pm/images/2527Thumbnail_huc91c0ceff46359598832c43766bcdd0f_366382_1600x0_resize_q75_box_3.png 3200w, /pm/images/2527Thumbnail.png 10000w" alt=“MockMotor service screenshot” />
External Test Environments Have Too Many Risks!
Have to be Reserved
Can't test against them if you didn't ask for them in time. Fill these environment reservation forms, please. It will only take you forever.
Have to be Retained
Late with your deliverable? Too bad, your environment is already reassigned to another project. We can spin you another one, at 5x the cost.
Have to be Seeded
The accounts in all these backends you use? They have to be in sync. A small mismatch, and you wasted a week tracking down an impossible defect.
Get Wrong Code
You need the R67 code in the backend, but they have R66 by mistake. Or added some funny local troubleshooting change. Your project's code goes crazy, and nobody can figure out why.
Suddenly Go Down
Tomorrow is the SFT exit, you have 15 defects to close, and the backend goes down for maintenance. Or for security patches. Or just goes down, for reasons unknown.
Can't Handle the Load
Your code makes 20 parallel requests to conform to the SLA for a large account, and your DEVs are proud of it. But the backend won't have it. It errors out on half of the requests and triples the RT for the rest.
Slow to Troubleshoot
You're positive the issue is with the backend. Three hours after opening a ticket, you get an email from their L1 support that asks you to reboot your servers, maybe? All 72 of them.
Cost a Bundle
And yes, the live backends cost hundreds of dollars a week. Each. And if you want to lease an LT-grade environment, there is an entirely different price list!
You have to deal with this anew every release. While the backends are not under your control, you cannot do any reusable configuration.
Microservices Make it Worse
Where before you had to arrange for and manage a dozen external test environments, with the microservices architecture, this number grows tenfolds. The downtime increases tenfold, too.
And remember that each microservice can be managed by a separate team. That means a separate chain of responsibility, separate point of contact, separate way of doing things, maybe a separate ticketing system.
In short, your woes grow in the order of magnitude. The old way becomes untenable.
Mock the APIs
Web services can be simulated (a.k.a mocked, a.k.a. virtualized). Instead of a live test environment, a configured mock service emulates the behaviour of the real service. For simplicity, it only emulates the operations needed for your project.
No Unnecessary Paperwork
No need to reserve or provision the services. Just add what you need to your mock environment, and you're set.
You Don't Have to Ask
All the virtualized services (mocks) belong to you. You create, update or delete them as needed for your project.
Seeding from One Spreadsheet
Guarantee the consistency by seeding from one file. If found an issue, fix it and seed again, right away!
You Control the Versions
Stable release, current PROD code or yet unreleased versions - you control what your application sees.
Mocks Never Down
Barring some system-level events, mocks never need to be down. Your project's blocks are minimized.
PT? LT? No Problem!
Mocks need no databases or other typical bottlenecks and can support a much higher load than the live systems.
Anything that goes wrong goes wrong under your control. The troubleshooting time is reduced to the bare minimum.
Won't Break the Bank
You don't have to pay for each backend separately. MockMotor costs a fraction of anything live.
Re-Use Until End of Times
Investments into mocks pay off the next release. And the next. And the next. Until the Sun becomes a red giant.
... We've saved weeks and $$$ in LT by using mocks instead of PROD-like backends.
Not Just for Experts
Your team are not developers? They are not the world’s leading experts in web services?
No matter! MockMotor was created with QA, LT and PT teams in mind.
MockMotor offers import tools for setting up first mocks within minutes. A typical input - a request and response pair, a WSDL or an OpenAPI file - can be used to create a mock instantly.
Co-Exists with Other Service Virtualizations
Your company already has an approved Three-Letter Corp Enterprise Service Virtualization Platform with its own team of ten and an onboarding process that takes two weeks?
MockMotor is not trying to undermine that investment.
Set up and tune the required responses on MockMotor by your own team. Once the responses are stable, you can transfer them to the service virtualization team.
Priced for Maximum Value
You can add more team members to MockMotor at any time - at no extra cost.
You can add more mock environments, more mock services, more mock responses - and the price still stays the same.
The longer you use MockMotor, the better value you’re getting!
Served Millions of Mocked Responses and Counting
MockMotor instances range from a couple of small services called a few times a day, to having dozens of environments, hundreds of services and hundreds of thousands of mock accounts with test runs sending production-like volumes.