Hoppscotch

What can you learn from the first response?

Pick a read-only request to a test copy of your own app. For a demo booking app, compare the status and the returned appointment times. A successful status tells you the request completed. The returned data tells you whether it completed the way you expected.

Save the request definition in a collection, which is a group of requests you want to run again. Give it a name such as Read test appointment times so the next person knows what it does.

Where can your requests, settings and secret values go?

Check how requests are sent before using a private test service. With a remote proxy, a separate service forwards requests and replies. Leave that option off for a private exercise. Check the address and confirm that it and any connected services are under your control.

A workspace is the area where you keep collections and settings. Hoppscotch says ordinary values in a shared environment sync to the server and are visible to workspace members. Values explicitly marked secret are entered by each user and are excluded from environment sync and export. The API still receives a secret if your request sends it. Keep real values out of the sample.

When would you pay, and what can you move?

The cloud Free plan includes a personal workspace, collections, environments and a runner for repeating saved requests. Business adds shared workspaces, collections and environments. The current annual price lists US$6 per user per month. Community Edition can run on infrastructure you maintain.

Export your collections and environment settings separately. Inspect the resulting files for fixed addresses and copied values before sharing them. Keep an independent copy of important sample responses, and confirm that a new tool can read the exported format before relying on it.

How can you rehearse the first request without sending it?

Draw a fictional appointment response on paper. Use no real address, account, proxy or connection.

1. 1
   Write what should come back

   Sketch a successful reply with 10:00 and 10:30 available. Write a second reply with the same success status and the wrong times.
2. 2
   Decide what would pass

   Mark the first response as a pass and the second as a failure. Keep a separate check for what the visitor actually sees on the page.
3. 3
   Plan what to save

   Save only the request name, sample data and expected outcome in your paper collection. Leave out keys and real addresses. If you later run it, use only the confirmed isolated copy of your own app.