LESSON VIEW
PQA-02 · LEVEL 1 FOUNDATIONS · PRACTICAL QA

The Tester Mindset and a Test Approach

Objective: Bring the tester mindset — curiosity, scepticism, empathy — and turn it into a one-page test approach: mission, scope in and out, top risks, oracles, and entry and exit criteria.

⏱ ≈1 h 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

  • Mindset = curiosity (ask), scepticism (verify), empathy (imagine the user).
  • Scepticism targets claims, not people — including your own first impressions and results.
  • An oracle is any source you check against: requirement, calculation, consistency, comparable product.
  • A test approach is decisions written down BEFORE testing: mission, scope, risks, method, data, criteria.
  • Scope is incomplete without an explicit OUT list.
  • One page, actually read, beats a binder nobody opens.

📖 Read

Tools change every year. The mindset underneath them is the durable skill, and it has three working parts. Curiosity generates questions the requirements never mention: what if a customer picks a date in the past, or changes the bedroom count after choosing a service? Scepticism disciplines that curiosity: when the site shows a Deep estimate, the sceptical tester calculates instead of thinking 'looks right' — Deep is 1.5× Standard (REQ-FN-01), so a 2-bed Deep must show $210 or something is wrong. Empathy keeps both honest: FreshNest's users are busy people booking on a phone, often distracted, and only a tester imagining that parent in Hamilton notices the form that is technically valid but confusing.

Every check needs an oracle — a source you use to recognise a problem: a requirement, a calculation, consistency with the rest of the product, a comparable product. And scepticism is aimed at claims and products, never at people: you are questioning the software, not attacking the developer or Maya.

Mindset becomes professional when it is written down as a test approach: your decisions, made visible before you start — what you will test, in what order (risk first), which techniques and oracles, what data you need, and what 'done enough' looks like (exit criteria). The trade-off is planning versus doing, and the balance point is one page: an hour of approach-writing saves many hours of wandering. The misconception to drop: an approach does not need to be a long formal document — a one-page approach the team actually reads beats a binder nobody opens.