extension ExtPose

API Response Simulator

CRX id

apcdhhdefemipnmdedjfbchkecliimpc-

Description from extension meta

Simulate API response to test your app's behavior

Image from store API Response Simulator
Description from store The API Response Simulator Chrome Extension allows you to simulate backend APIs in order to test how your application handle API certain response. Generally, if you want to test how frontend behaves when backend API returns 2xx, 4xx or 5xx status codes, there are two options: - If you control the backend, you can patch your backend code and manually return 2xx/4xx/5xx status codes from API methods. - If you don't control the backend, you can patch your frontend code with some debug statements to verify the behavior. Neither of which is an elegant approach. The API Response Simulator Chrome Extension allows you to map backend API endpoints to the responses you want to simulate for your application. Internally it patches browser's native XMLHttpRequest API. Once you've installed the extension, follow the steps to operate it: - Click on the ! icon at right top of the browser and switch on the extension. - Click on the OPTIONS button. It'll open a page where you can supply rules with: - The combination of URL and HTTP verb - The response status code - The response value - You can also edit/delete your rules Note: Please ensure you turn off the extension after its use. Leaving this extension on might hijack and break your API calls due to the nature of its implementation. Design Credit: Name: Jainul Abedin LinkedIn: https://www.linkedin.com/in/jainul-abedin-4148b816 Email: [email protected]

Latest reviews

  • (2021-11-15) ka K: nie działa
  • (2021-10-25) Chirag Pandit: Hi Anup, qq How do I pass in partial URL match? Is there a documentation where I can read more about how are you matching the URL path? Eg: I want to mock a scenario where the following book creation API fails https://mybooks.io/library1/book INSERT 200 https://mybooks.io/**/book INSERT Should return 500
  • (2021-06-29) Rob Davis: This never worked for any of the endpoints I manually entered. However after 2 months of Google Maps not working in Chrome, I realized that this extension was blocking all of Map's API calls. Uninstalled the extension and Maps started working just fine. Reinstalled the extension just to leave this review, now I'll be removing it again.
  • (2021-03-02) Dieter Ivo Brodien: Great, works as expected. Thanks! One feature would be really useful though: Make a toggle to enable or disable rules.
  • (2020-11-27) Ruud Landman: Awesome extension. The interface could be improved (for instance: list box for status code and more space for entering the mocked data), but the most important thing is that it does what it needs to do and it does it perfectly. Other similar extensions mostly give CORS errors/problems but this one does not!
  • (2020-10-26) Christopher Griebel: Worked exactly as expected for my needs. I was able to produce and test 401 and 403 errors in a react application using axios. I didn't experience any of the issues that the other reviews mention.
  • (2020-10-09) Ivan: Worked very well for me. I simply added api URL, status 200 and inserted required response JSON. That's it.
  • (2020-09-25) Jake Mager: Exactly what I was looking for!! Thank you :) Works like a charm
  • (2020-09-02) Alexander Stuart: Doesn't work
  • (2020-08-14) Niklas H: When this extension is active it blocks random XHR requests from my browser. Just now I activated the extension (with the default config) loaded a page, and noticed that it broke cause some requests were blocked.
  • (2020-08-07) NE debug: Lot of potential, but not working. I've read your replies to earlier reviews. I created a rule to intercept a (real) API and inject a canned response for testing, however the API response inside the code is still whats in the real API response, not the expected injected value.
  • (2020-04-08) Ashish Patel: Userless extension. not working at all.
  • (2020-04-06) Glenn Dwiyatcita: Ain't working for me. Nice try, though! :) Steps to reproduce: 1. Add GET rule against https://example.com with simulated 404 response code. 2. Visit https://example.com with the extension turned on. 3. Still got HTTP 200 OK success status response code instead of simulated 404.
  • (2020-01-29) Ole Frank Jensen: Doesn't seem to be working. Localhost calling external api, defined a rule for the exact URL simulating http 400 Bad Request. But still gets 200 OK and data from that endpoint.
  • (2020-01-13) This looked like exactly what I needed, but unfortunately it doesn't seem to work at all :(
  • (2019-12-18) Jainul Abedin: Loved It
  • (2019-12-13) Monika Pant: very helpful while project development in scenarios where we need to simulate BE error and implement error handling

Statistics

Installs
1,000 history
Category
Rating
3.2 (18 votes)
Last update / version
2021-08-09 / 0.2.0
Listing languages
en

Links