Objective: Define quality, testing, verification and validation in plain language — and rank what to test first by risk (impact × likelihood) instead of spreading effort evenly.
⏱ ≈45 min full lesson · Practice site: FreshNest booking form · English edition — Español · العربية · বাংলা in translation
🧽 The practice business: FreshNest Home Cleaning — a fictional local cleaning company (owner: Maya Torres) invented for this course. Every example and exercise uses FreshNest, so you learn on a complete, realistic business without ever touching a real one.
Quality is not something a tester inspects into a product at the end, and it is not the same as 'no bugs.' For FreshNest, quality means a customer gets an accurate quote, completes a booking without confusion, and leaves a phone number Maya can actually call back. A site could have zero crashes and still be poor quality if its prices mislead people.
Testing is not proving the product works. Testing is an investigation: you explore, ask questions, run checks, and report what you find so someone — Maya, a developer, a manager — can make a good decision. Inside it sit two kinds of checking. Verification compares the product with its written requirements: does the phone field require a 10-digit number (REQ-FN-02)? Validation compares it with real human needs: does a busy parent in Trenton understand the quote, and does the Move-Out message read as helpful rather than a brush-off? A product can pass verification and fail validation.
Because you can never test everything, you think in risk. Risk combines how bad a failure would be (impact) with how likely it is (likelihood); multiply simple scores and you get a ranking that tells you where to look first. The trade-off is depth versus breadth: every hour digging into the quote estimator is an hour not spent on the date picker. And the standing misconception to drop now: a passing suite does not prove there are no bugs — it only shows the checks you ran did not fail.