WireMock Cloud

What do you like best about the product?

Our team has had a very positive experience using WireMock. It’s reliable, easy to use, and has helped streamline our development and test automation processes. We appreciate how much smoother and more reliable our test automation have become since we started using WireMock. They are eager to listen our feedback and fast to iterate over new functionality that might be missing.

What do you dislike about the product?

Nothing that would so far jump to my mind.

What problems is the product solving and how is that benefiting you?

We have multiple data sources that our application integrate to and the testing data between these services are not consistent. We also don't want to cause any extra load to our data sources, and WireMock allows us to solve both getting consistent mock data and being reliable available when needed.

What do you like best about the product?

Having previously used the WireMock desktop tool, I was already a fan of the core functionality. But the lack of a built-in interface made API creation difficult. WireMock Cloud solves this by offering a simple web interface that makes the entire process incredibly easy. The web application allows us to get new mock endpoints up and running quickly, which has greatly increased our development speed. We really like the request recorder, which is excellent for quickly creating mocks of existing API integrations. The response body templating is also a powerful and robust feature, useful for simulating a wide range of real-world scenarios. Honestly, I can't think of any features I'd like added; the product covers all our needs very well.

What do you dislike about the product?

A few small nitpicks. The pricing structure, which incorporates both user and request limits, can be a little confusing at first. However, the company has been very accommodating and willing to work with us when overages occur. Also, it can be difficult to find specific request endpoints in the application, especially when an API has a large number of them. Finally, we’d appreciate a feature that provides a history of changes to endpoints, including who made the changes, for better team collaboration and auditing.

What problems is the product solving and how is that benefiting you?

Our company works with third-party services a lot. We set up Mock APIs for each of our integration partners to help with development and QA. Each partner has its own peculiarities and nuances, but we are able to set up mock endpoints to easily test both standard workflows and edge cases. For instance, our team recently added an SSO login feature to the product. Wiremock's OpenID Connect one-click deployment template allowed us to quickly create an OpenID Connect API for development and testing.

What do you like best about the product?

It helps in mocking the Api's and we can add json so that it can send mock response the same way we want.

What do you dislike about the product?

It can consume a significant amount of resource while you are running it in your computer, which may slow down the performance of the computer.

What problems is the product solving and how is that benefiting you?

When we are developing an application, we have to develop both frontend and backend. While developing front end, we need some mock data to efficiently develop the front end. If the backend is not ready, we can use wiremock to mock the api and use it for developing front end.

What do you like best about the product?

All mocking features of the WireMock OSS made easy using an online interface. What stood out is the ability for the product to upload and manage data sources almost similar to a mini DBMS. It has a good knowledgebase which makes it easy to integrate. And the WireMock cloud team is always ready to answer questions.

What do you dislike about the product?

None at this stage as WireMock ticks all our API mocking requirements.

What problems is the product solving and how is that benefiting you?

API mocking, Integration testing, Parallel development with different teams, Stateful API mocking, Fake data generation, Fake data management, and Hard to recreate errors like network errors.

What do you like best about the product?

Idiomatic mocking for writing integration tests

What do you dislike about the product?

A lot of configuration boilerplate required to set-up

What problems is the product solving and how is that benefiting you?

Helps in writing mocks for integration tests