QA vs QC vs testing
Updated 2026-11-13 · 2 min read
Understand assurance, quality control and testing without confusing job titles with the activities a team performs. Includes a comparison table, concrete examples and an interview answer.
The difference in one table
| Aspect | QA | QC | Testing |
|---|---|---|---|
| Emphasis | Confidence in the way quality is achieved | Checking whether quality requirements are met | Evaluating work products and finding problems |
| Typical focus | Processes and how they are followed | Product results and corrective action | Risks, expected behaviour and actual behaviour |
| Example | Improve a requirement-review process | Evaluate release evidence against criteria | Exercise invalid coupon cases |
| Output | Agreed practices and improvement actions | Acceptance decisions and nonconformities | Findings, results and coverage evidence |
| Ownership | Shared; assurance specialists may support it | Shared; quality specialists may support it | Testers, developers and other participants |
Examples
QA: repeated coupon misunderstandings lead the team to add examples and a review step to discount requirements. Check later whether that process is being followed and helps expose ambiguity.
QC: before release, inspect the coupon feature and its evidence against agreed quality criteria. An incorrect discount is a product problem to resolve.
Testing: design and execute eligible, excluded and expired-coupon cases to discover that incorrect discount. This supplies evidence used by QC; testing does not by itself guarantee the process or the product is defect-free.
How to answer in an interview
QA focuses on providing confidence through the processes used to achieve quality. QC focuses on checking whether the product meets quality requirements, and testing is an important activity that supplies that evidence. For example, requirement-review improvements support QA, while coupon tests reveal product problems used in QC decisions. In job titles, “QA” often means a tester, so I distinguish the title from the activity.
Common confusion
“QA prevents all defects; QC only detects them” overstates the separation. Findings from product checks can improve the process, and a good process cannot guarantee a perfect product. Do not present testers as the only people accountable for quality.
Likely follow-up: Can the same person do all three? Yes: a tester can improve review practices, examine release evidence and execute tests, while keeping the purposes distinct.
This is independent foundation-level learning material, not affiliated with ISTQB.
Quick answers
Is QA just another name for manual testing?
No. Manual testing describes how a test is executed; QA describes an assurance purpose. A company may still use QA as its tester job title.
Can testing prove quality?
Testing provides bounded evidence about the conditions examined. Release decisions also consider requirements, risks and gaps in that evidence.
Sources
Want a project you can show in interviews?
The portfolio project kit walks you through testing a deliberately buggy app with Selenium or Playwright and API tests, then explaining it. The app itself is free.