LESSON VIEW
PQA-07 · LEVEL 2 PRACTITIONER · PRACTICAL QA

Testing a Web App End to End

Objective: Test one complete user journey — form fields and form states, a second browser and a phone-width screen, keyboard-only accessibility basics — and record every check in a traceability matrix that ties requirements to results.

⏱ ≈75 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.

⚡ Key Points

  • Test the journey, not the buttons: quote → booking → confirmation.
  • Fields get valid / invalid / boundary values; states get empty, Back, refresh, double-submit.
  • A second browser and a phone width are part of the check, not a luxury.
  • Keyboard-only completion is the fastest honest accessibility check there is.
  • Errors must name the field, describe the fix in text, and be announced to screen readers.
  • The traceability matrix is the coverage proof: requirement → case → result, no empty cells.

📖 Read

Testing a web app end to end means acting like a customer with a job to do — for FreshNest, getting a cleaning booked — and checking every step of that journey, not just individual buttons. Most web failures live in forms. Test each field for valid, invalid and boundary input; then test states: submit an empty form, go Back after submitting, refresh mid-journey, double-click submit. A good app always knows its state and never loses the customer's details or books twice.

Your customers are not all on your laptop's browser. Run the full journey once in your main browser, then repeat the highest-risk steps — price display, form errors, the booking confirmation — in a second browser and at a phone-sized screen. Depth on the journeys that take money or personal details; breadth, a quick pass, everywhere else.

Accessibility essentials, in WCAG 2.2 AA terms: perceivable (contrast; text alternatives for meaningful images), operable (everything works from a keyboard alone, and focus is always visible), understandable (visible labels; errors name the field and say how to fix it), robust (screen readers can announce labels, errors and confirmations). You don't need to be a specialist to check the basics: unplug the mouse and try to complete the booking with Tab, Enter and the arrow keys. The misconception to drop: 'it worked in my browser, so it works' — your browser has your screen size, your saved data, your fast connection. Customers bring none of those.