Requests Last Week
Developers are often blocked waiting for third-party APIs to be delivered.
Integration or acceptance tests may fail due to dependent APIs being unavailable.
Creating self-hosted mocks involves not only the implementation of their business logic but also other boilerplate, time-consuming tasks.
It can be challenging to test failure integration scenarios with live systems.
SMS, email sending, or any other billable transactions may generate additional costs.
Setting up a state in a live system may be a time-consuming process that lengthens the time needed to execute a test suite, and slows down the test feedback loop.
You don't need a credit card. We have a Free plan for those who want to check what is SmartMock.io and how to use its features to deliver more reliable software faster.
Create or import your first workspace. You may specify your own or generate a random subdomain which creates an HTTP(S) address uniquely identifying a particular workspace.
Adjust or add mocks using one or more request-matching mechanisms like comparing the path, query parameters, or header values.
Copy a workspace's HTTP(S) address and add it to the configuration file of the service you would like to test. Now you are ready to run tests without the need to call live third-party services.
How many times have you contacted third-party applications asking for the status of their test environment because your acceptance tests failed? Use SmartMock.io to simulate third-party APIs get accurate test results checking your system's behavior and not the whole neighborhood.
You don’t have to wait for a third-party API to be implemented, tested, and deployed. Just grab its documentation in Open API 3.0 or Swagger format, use import feature of SmartMock.io, tune the outputs, and start consuming the mocked service.
Creating, maintaining, and troubleshooting self-hosted HTTP mocks consumes a considerable amount of time and effort. Every mocked API is different, and you must implement its unique logic differently. We believe the business logic of your HTTP service mock is the only thing you should care about. Implement it with SmartMock.io using Static, Template, or Dynamic mocks. You focus on the production code. We handle the rest.
You may share your HTTP mocks with your teammates. Your business partners can set up HTTP API mocks so you can test integration with their systems. You can also create mocks for your business partners to consume while you are still developing or testing your service.
Workspaces are isolated containers for your mocks. Each workspace has a unique URL assigned (you choose the subdomain name). You can create a workspace for each API and environment you are mocking to simplify mock management and maintenance.
Use SmartMock.io and Open API description to allow consumers to test your API design before its implementation. Receive feedback from API consumers faster.
It’s important to test how your services behave in unfavorable or extreme conditions, like errors, timeouts, or unexpected responses being returned by the third-party services you integrate with. Verify how your services react to heavy loads without the need to reach live third-party APIs which might not be capable of handling high traffic or require scheduling for testing. SmartMock.io matching rules let you return various outputs depending on request field content (HTTP method, body, headers, query parameters, cookies).
We’ve all experienced it. You prepared your demo carefully and you expected to impress the audience, but during the demo one of the service providers failed. It’s embarrassing. Mock third-party dependencies with SmartMock.io and make your demos smooth and impressive.