THE RESULT YOU'RE WORKING TOWARD
Done means it works.
The failing boundary is identified and a retest produces the intended result once.
Practice project: A staging copy of Harbor01 / GET READY
Before you start.
- Platform / editor
- Your existing website platform and integration tools
- Access & plan
- Authorized access to a test copy, site records and relevant accounts. Live restore, access changes and publication need owner approval.
- Starting point
- Complete the previous lesson or use an equivalent prepared demo project.
Keep a note of the exact account, project and version you use. Work with demo data and record the expected result before making changes. Never place passwords, verification codes or private customer records in your evidence.
02 / LEARN THE TOOL
Open the official walkthrough.
Use the publisher's instructions and available screenshots to locate the current controls. Then return here for the SETLY exercise and its result checks. These links open on the publisher's website.
Source credit belongs to the named publisher. These are external references, not SETLY recordings or a claim of affiliation. Screen names and plan availability can change.
03 / PUT IT INTO PRACTICE
Your task, step by step.
Use one labelled demo record or project so you can find your work again. Finish each action before continuing; if the screen differs, consult the matching official source rather than guessing.
- 01
Step 1
Write the expected event, source system, destination and observable output. Choose one labelled test record.
- 02
Step 2
Inspect source execution, outbound request status and destination logs in order. Record the first place where observed behavior differs.
- 03
Step 3
Check credentials, field mapping, rate limits and recent changes only where the evidence points. Keep secret values out of screenshots and notes.
- 04
Step 4
Correct the diagnosed issue and replay a controlled test with duplicate protection. Verify the destination result before closing the incident.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If a retry creates duplicate work, stop replaying and implement or verify a stable event identifier before continuing.
My screen is different from the guide
Check the product, editor, account role and selected project first. Open the credited official instructions for your version. Record the difference and pause any action whose effect you cannot verify.
The screen looks correct, but the result is missing
Inspect the saved record, published page or execution log that should prove the action. A preview, success message or draft is not always evidence that data was stored or a message was delivered. Retest with one unique demo value.
05 / PROVE THE RESULT
Check it before you call it done.
The failing boundary is identified and a retest produces the intended result once.
Keep useful evidence
Record the test date, project/version, expected result, observed result and a non-sensitive screenshot or record reference. Mark anything you did not test as untested. Your checkmarks do not certify an untested result.
Download the editable verification checklist ↓Guide status: original written practice exercise with credited external references. SETLY screen recording and independent learner reproduction are not yet complete.