THE RESULT YOU'RE WORKING TOWARD
Done means it works.
Every required case has an observed pass, or a clearly documented unresolved defect that prevents release.
Practice project: Harbor Home Care01 / GET READY
Before you start.
- Platform / editor
- HTML, CSS and JavaScript; Python local preview server
- Access & plan
- Text editor, modern browser and Python for local preview. Hosting and form-backend accounts are needed only for their corresponding lessons.
- 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.
Download website starter ↘ Open completed static example ↗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
Create a checklist covering navigation, keyboard use, form behavior, images and mobile layout. Define the expected result before testing.
- 02
Step 2
Run each case on the local build and approved hosted copy. Record a screenshot and the exact reproduction steps for failures.
- 03
Step 3
Fix one underlying cause at a time. Repeat the failed case and one nearby related case after each change.
- 04
Step 4
Ask another person to find a service and contact the business without hints. Record where the wording or navigation caused confusion.
Inspect padding, border and margin when a layout overlaps or has unexplained spacing.
Source: Mozilla Contributors / MDN Web Docs. CC BY-SA 2.5 or later; unchanged.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If a fix works only on your machine, compare URLs, versions and stored browser state before editing more code.
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.
Every required case has an observed pass, or a clearly documented unresolved defect that prevents release.
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.