Before each exercise, make sure Capture is running for this page in PayloadPigeon. If you see Not capturing, click Start capture this tab. If Capture is already running, leave it on.
In each example, you will change a request or response, save the setup as a Test, run the saved Test, and record the outcome.
Step 1 of 5
Test how the app handles an error
ON THIS PAGE
Click Reset example, then Send HTTP request, and wait for the normal 200 OK response.
Go to the working area ↓
IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/message sent from this page.
2. In the response details, click Modify & test.
3. Set Response behavior to Apply only this changes to the fresh response. Leave the response JSON unchanged, set Status to 503, and click Ready.
ON THIS PAGE
Click Send HTTP request again. The page should receive HTTP 503 and show its HTTP-error state.
Go to the working area ↓IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
2. Choose the Playground Test Plan, enter HTTP 503 response, and click Save.
IN PAYLOADPIGEON
3. Open Test Plans → Playground and find HTTP 503 response.
If PayloadPigeon asks you to protect or unlock saved data, complete that step in the extension and continue saving. See Save the Test in the first tutorial for details.
IN PAYLOADPIGEON
4. Click Ready on HTTP 503 response.
ON THIS PAGE
Click Send HTTP request and check that the page again shows its HTTP 503 error state.
Go to the working area ↓IN PAYLOADPIGEON
5. Return to Current Test at the top of the Side Panel. If the page shows the expected HTTP 503 error state, click Works correctly. Otherwise click Found a problem, describe the difference under WHAT WENT WRONG?, and click Save result.
6. Open Results, find the latest row named HTTP 503 response, and click the entire result row to open it.
CHECK
The opened Result is named HTTP 503 response and contains the outcome you selected.
Step 2 of 5
Test server validation
ON THIS PAGE
Click Reset example, then Send HTTP request, and wait for the normal 200 OK response.
Go to the working area ↓IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/message sent from this page.
2. Click Modify & send in the request details.
3. Change count from 1 to -1. Leave the other fields unchanged and click Send.
IN PAYLOADPIGEON
In Current Action, click Show sent request in Traffic →. The server reply should be HTTP 400 with JSON code INVALID_COUNT.
IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
2. Choose the Playground Test Plan, enter Invalid count, and click Save.
IN PAYLOADPIGEON
3. Open Test Plans → Playground and find Invalid count.
If PayloadPigeon asks you to protect or unlock saved data, complete that step in the extension and continue saving. See Save the Test in the first tutorial for details.
IN PAYLOADPIGEON
4. Click Send on the saved Invalid count Test and inspect the new reply using Show this run in Traffic →.
5. Return to Current Test at the top of the Side Panel. If the reply is 400 with INVALID_COUNT, click Works correctly. Otherwise click Found a problem, describe the difference under WHAT WENT WRONG?, and click Save result.
6. Open Results, find the latest row named Invalid count, and click the entire result row to open it.
CHECK
The opened Invalid count Result contains the selected outcome. A 400 with INVALID_COUNT is the expected server-validation behavior.
Step 3 of 5
Change response data
ON THIS PAGE
Click Reset example, then Send HTTP request, and wait for the normal 200 OK response.
Go to the working area ↓IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/message sent in the previous step of this exercise.
2. Open Modify & test in the response details.
3. Set Response behavior to Apply only this changes to the fresh response, change only items to [], and click Ready.
ON THIS PAGE
Click Send HTTP request.
Go to the working area ↓IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
2. Choose the Playground Test Plan, enter Empty response list, and click Save.
IN PAYLOADPIGEON
3. Open Test Plans → Playground and find Empty response list.
If PayloadPigeon asks you to protect or unlock saved data, complete that step in the extension and continue saving. See Save the Test in the first tutorial for details.
IN PAYLOADPIGEON
4. Click Ready on the saved Empty response list Test.
ON THIS PAGE
Click Send HTTP request. Check that the response again contains items: [] and the page shows Empty response list.
Go to the working area ↓IN PAYLOADPIGEON
5. Return to Current Test at the top of the Side Panel. If the empty-list message appears, click Works correctly. Otherwise click Found a problem, describe the difference under WHAT WENT WRONG?, and click Save result.
6. Open Results, find the latest row named Empty response list, and click the entire result row to open it.
CHECK
The opened Empty response list Result contains the outcome you selected.
Step 4 of 5
Test a delayed response
ON THIS PAGE
Click Reset example, then Send HTTP request, and wait for the normal 200 OK response.
Go to the working area ↓IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/message.
2. Click Modify & test in the response details.
3. Set Delay (ms) to 5000 (5,000 ms), leave the response content unchanged, and click Ready.
ON THIS PAGE
Click Send HTTP request and watch the page wait for the response. When the reply arrives, the page shows the result and elapsed time.
Go to the working area ↓IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
2. Choose the Playground Test Plan, enter Delayed HTTP response, and click Save.
IN PAYLOADPIGEON
3. Open Test Plans → Playground and find Delayed HTTP response.
If PayloadPigeon asks you to protect or unlock saved data, complete that step in the extension and continue saving. See Save the Test in the first tutorial for details.
IN PAYLOADPIGEON
4. Click Ready on the saved Delayed HTTP response Test.
ON THIS PAGE
Click Send HTTP request and check the wait followed by the normal reply.
Go to the working area ↓IN PAYLOADPIGEON
5. Return to Current Test at the top of the Side Panel. If the page waits about five extra seconds and then receives the normal reply, click Works correctly. Otherwise click Found a problem, describe the difference under WHAT WENT WRONG?, and click Save result.
6. Open Results, find the latest row named Delayed HTTP response, and click the entire result row to open it.
CHECK
The opened Delayed HTTP response Result contains the outcome you selected.
Step 5 of 5
Test a missing response
ON THIS PAGE
Click Reset example, then Send HTTP request, and wait for the normal 200 OK response.
Go to the working area ↓IN PAYLOADPIGEON
1. Open Traffic → HTTP and select the latest POST /playground/api/message sent from the page.
2. Click Modify & test in the response details.
3. In Behavior, choose Drop matching request and click Ready.
ON THIS PAGE
Click Send HTTP request. Instead of a normal reply, the page should show a request error. If the browser does not end the operation sooner, the page reports a timeout.
Go to the working area ↓IN PAYLOADPIGEON
In Current Action at the top of the Side Panel, check for APPLIED and Request dropped.
IN PAYLOADPIGEON
1. In Current Action for the change you just applied, at the top of the Side Panel above the navigation, click Save as Test.
2. Choose the Playground Test Plan, enter Dropped HTTP response, and click Save.
IN PAYLOADPIGEON
3. Open Test Plans → Playground and find Dropped HTTP response.
If PayloadPigeon asks you to protect or unlock saved data, complete that step in the extension and continue saving. See Save the Test in the first tutorial for details.
IN PAYLOADPIGEON
4. Click Ready on the saved Dropped HTTP response Test.
ON THIS PAGE
Click Send HTTP request and wait for the request error or timeout.
Go to the working area ↓IN PAYLOADPIGEON
5. In Current Test, check for Applied · Request dropped. Click Works correctly if that indicator and the expected page error are present. Otherwise click Found a problem, describe the difference, and click Save result.
6. Open Results, find the latest row named Dropped HTTP response, and click the entire result row.
CHECK
The opened Dropped HTTP response Result contains the outcome you selected.
