Media
5 items
Description
Hassle-free mocking of xhr and fetch calls. Mocking your API responses like a pro. The Parrot browser extension allows you to mock any asynchronous call you like. Using its network viewer you can monitor all calls being done, and with the ease of just one mouse button click you can start mocking every call you need to be mocked. Works for both old-school XmlHttpRequest and modern Fetch-API calls. Mocking can be as easy as just pasting alternative JSON payloads to be returned by the call, or by doing more complex transformation of responses using JavaScript. Whether or not mocking needs to take place can be decided by comparing the URL with a matching string or regular expression or, if a more fine-grained approach is needed, by inspecting the request using JavaScript. 💡 When to use this extension? 🔸 You are developing a front end that needs to connect to some back end API, but that API has not yet been developed or is down. 🔸 You want to give a live demo but the back end API needed is currently not available or broken. 🔸 You would not only like to test the happy flow, but would also like to see how your front end behaves given any possible alternate scenario or edge case. 🔸 You are experiencing a nasty bug but have no way of reproducing it easily using the real back end system. You would like to tweak the response to check if any unexpected response could be the cause of your issue. 💡 How to use this extension? Just make sure you have the Parrot the network viewer (see below) option enabled and start your journey. Any API-call done will showup in the viewer and can be mocked by the click of one single button. As an alternative, you can also start by pressing the "Define your mocks" button and then pressing the Add button to define a mocked response for a specific request. A line will show up on which you can define the HTTP verb/method and the URL-fragment of the request you would like to be mocked. The URL fragment is defined with a regular expression, allowing you to make any matching requirement as loose or strict as you would like it to be. NB In cases where the request also has a payload (like POST), the content of that payload can be used for determining if mocking should take place. On that same line you can then define the status code of your response, the exact response type and the payload to be returned. Once the extension detects the method/URL you expressed, the regular call will still be done. However, once the actual response has been received, no matter it's actual result, it will be replaced by the mocked response you defined. NB Next to being JSON, for any response also SCRIPT can be specified. In this case plain JavaScript statements can be defined with which the original response can be modified (you can just reference the contextual variable "response"). Example (note that no function or return statement is needed): response.someProperty = 'someValue'; response.someArray.push('blabla'); 💡 JSON5 Parrot uses JSON5 (https://json5.org) to allow for a less strict JSON-format. This means that typical JavaScript JSON-responses can be copied and pasted with ease. No need to use quotes around properties. If used, quotes can be single or double. Dangling comma's are allowed and you can even have comment in your JSON-structure. 💡 Multiple mock rules When determining the mock data to be substituted, there can be multiple rules matching the given URL and method. By default, Parrot will just cycle through the available mocks in top-down order. You can easily change this behavior by always selecting the first available mock, always selecting the last available mock, randomly picking one of the available mocks or sequencing through them. 💡 Timing your calls by adding a delay Particularly for checking for, or debugging of, potential race condition issues, for any request a delay (expressed in milliseconds) can be specified. This delay will be taken into account before the response is returned to the client that made the request. By carefully timing request/response cycles you can make sure that responses will be received in the exact order you would like them to be. 💡 Export and Import your mock rules The set of mock rules can also be exported to the file system using the Export button. This allows you to share your mock data with others and also allows you to create/maintain sets of mock rules. Exported files can easily be reimported by using the Import button. Imported files will be appended to any currently existing mock rules in the extension, allowing you to stack multiple sets on top of each other. 💡 Notification when mock data has been used Every time mock data has been substituted, a small notification will show up. This behavior can be turned off using the popup dialog. The notification will show the path that's being mocked, the number of mock rules applied on it's response and, if applicable, the delay that was taken into account. 💡 Network viewer Parrot will show all asynchronous calls in a compact view directly attached to your content page. This network view offers you the possibility to show and mock any response with the click of one single button. The overview also directly shows which responses were mocked and which responses were original. In case of a mocked response, opening the mock dialog will show you the response that resulted after applying all involved mock rules. 💡 Localhost Localhost resources will not be mocked by Parrot.