What you will learn
You have learned to read JSON, separate syntax from validation, and compare simulated creation with read-back. Now combine those skills. You choose the sequence from the evidence requirements; there is no Prepare guide.
Your goals
- Plan and execute a public API investigation independently.
- Make a conclusion from paired request and response evidence.
Before you start
Read the previous lesson first if you have not already. This course does not require programming.
Practice setup
These requests use the public TestKru teaching API. No workspace is needed unless a step says so. Leave the body empty for GET, HEAD and OPTIONS. Example people and emails are fictional. Changes to /api/users are simulated and are not saved.
Supplied training evidence / contract
Contract: /echo parses JSON and returns supplied data without storing a customer. Legacy /users creation is simulated. Your investigation must distinguish malformed JSON from readable JSON and a successful create reply from persistence. A reproduced observation is not automatically a defect.
Follow these steps
- Write four cases in your notes before sending: readable echo, malformed echo, simulated user create and read-back. For each state method, URL, body, expected contract and evidence needed. Use the evidence slot labels as scope, not as a request sequence.
- Execute from the empty console. Use Content-Type application/json for the POSTs. The malformed sample is {"name": with no closing value or brace; choose a fictional name and a numeric age for your valid echo body.
- For user creation, choose your own valid fictional name and email. Read the returned id and use it for the follow-up GET; the static teaching fixture currently returns 6. If that fixture changes, report the contract difference rather than selecting an unrelated record.
- Select the four named responses. Record the create id and read-back status, and classify the persistence evidence. Submit.
- Use self-review to write a concise finding or clarification, include expected versus observed, and say what you did not test. A completion score verifies these facts, not the professional quality of your report.
Investigate before concluding
First record the actual result for each case. Compare the body, headers and later state with the stated contract. Keep an observation separate from a prediction; use the model answer only after making your own attempt.
What to keep as evidence
- Readable and malformed JSON have distinct executed evidence.
- The follow-up targets the id actually returned by creation.
- The report cites the simulation contract and names limits.
References for this lesson
Finish this assignment
Select each named response in the evidence dropdowns. Answer from those responses or the transcript on this page. Click Submit Answers. Your score is the percentage of checks that passed. Core checks are required to finish. Extra evidence checks are labelled. A saved 100/100 means every check passed. Continue opens the next lesson you can submit.
If something goes wrong
- Change one part of the request at a time. If a check needs attention, read the note under it and compare it with the response you selected.
Self-review and independent variation
- Readable and malformed JSON have distinct executed evidence.
- The follow-up targets the id actually returned by creation.
- The report cites the simulation contract and names limits.
After finishing, repeat with a different fictional user name and explain whether the persistence conclusion changes.
Automatic checks verify the requests and answers configured for this lesson. The self-review is for your own reasoning. A score is not a certificate.