Skip to content
CodeKruPro

Test normalized duplicates and real deletion

25/32

04 · Design cases and verify stored changes

Recommended first: Prove replacement and partial changes were saved

Your goal: Test normalized duplicates and real deletion

Continue one saved customer through the named test cases.

  1. 1Set up data
  2. 2Send requests
  3. 3Submit answers

Start here: sign in to practise.

Jump to practice

What you will learn

Continue the saved-customer workflow from create/read-back. This lesson uses its own workspace, so obtain fresh tokens and IDs. A mutation response and a later read are separate pieces of evidence.

Your goals

  • Build a request from the rule rather than copying an answer.
  • Keep observed evidence separate from the expected result.

Before you start

Read the previous lesson first if you have not already. This course does not require programming.

Practice setup

Click Create workspace. Then log in as the fictional customer named in the steps. Use that practice token, not your CodeKru sign-in. Reset starts this lesson’s data over and invalidates its tokens.

Follow these steps

  1. Create the workspace, log in as A and create the supplied customer. Select its response and copy its id.
  2. Try another create using the same email in uppercase with surrounding spaces. Keep name valid. Select its response. Read the original id and select its response to compare values.
  3. Delete that exact id and select its response. Send a later GET of the same id, select it, and then repeat DELETE and select that response too.
  4. Record both deletion statuses and submit. A second delete can have a different status while the stored effect stays the same.

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

  • Each selected response belongs to its named case.
  • Conclusions follow the request and response evidence.
  • Another learner can repeat the work using the stated setup.
References for this lesson

Finish this assignment

Answer from the transcript on this page. Click Submit Answers. Your score is the percentage of checks that passed. 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.
  • A 401 means the practice login token is missing or expired. Log in again in this workspace.
  • A 409 on create means that fictional email is already used. Choose another email.
Self-review and independent variation
  • Each selected response belongs to its named case.
  • Conclusions follow the request and response evidence.
  • Another learner can repeat the work using the stated setup.

Use another fresh lesson workspace to discuss uniqueness scope without touching another learner’s data.

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.

Open API reference

Practise and save your evidence

The lesson is public. Sign in to send requests and save progress. You will return to this lesson.

Sign in to practiseCreate an account