What Is Quality Assurance?
Basketly is a grocery-delivery web app: you log in, search for products, fill a cart, apply the coupon SAVE10 and check out. Last month a customer got 10% off a ₹200 order, even though the coupon is meant only for carts of ₹500 or more. Someone asks, "Didn't QA test this?" That question hides a misunderstanding about what QA actually is.
The rule
Testing finds defects; quality assurance stops them being made.
Three words get mixed up all the time. Here they are, from widest to narrowest:
- Quality assurance (QA) looks at the process. It asks: how do we build software so that fewer defects get in? Clear requirements, reviews, agreed definitions of done and good habits are all QA.
- Quality control (QC) looks at the product. It checks a finished piece of work against the standard before it goes out.
- Testing is the main QC activity: running the software with chosen inputs and comparing what happens with what should happen.
And quality itself means more than "no crashes". Software has quality when it does what its users actually need, reliably, safely and in a way they can use. A checkout that never crashes but charges the wrong price is not quality.
A QA engineer therefore does far more than click buttons at the end. They join early conversations, question vague requirements, help decide what "done" means, and then test, report and learn from what escaped.
The shortcut
For any activity, ask one question: does it change how we build, or does it inspect what we built? Changing how we build is assurance. Inspecting the result is control, and testing is the main way to inspect.
Before coding: the requirement review
Nobody asked what happens below ₹500. A review that raised this question is QA: it improves the process so the bug is never written.
The trap is thinking QA only starts when the code is finished. By then the cheapest moment to stop the coupon bug, a single question in a planning meeting, has already passed.
Drills
Answer fast — trust the rule.
Which activity is quality assurance rather than testing?
What does testing compare?
Basketly's checkout never crashes but adds tax twice. Does it have quality?
When is the cheapest moment to stop a missing-minimum bug like the coupon one?
Remember
- Testing finds defects; quality assurance stops them being made.
- Ask: does this change how we build (QA) or inspect what we built (QC and testing)?
- QA starts at the first requirement, not when the code is finished.