QA, QC, Testing, Verification, and Validation: What Is the Difference?
Confusion over basic terminology is common among new QA engineers. Interviews, courses, and teams often use QA, QC, testing, verification, and validation interchangeably, making them seem equivalent. They have different meanings.
This article explains those differences in plain language with practical examples.
Why these terms are often confused
First, one person in a small team often does everything: analyzing requirements, writing test cases, checking the product, reporting bugs, and discussing processes. This blurs conceptual boundaries.
Second, job listings and everyday conversation often use QA as a job title, although quality assurance has historically covered more than manual testing.
Third, many people enter the profession through testing and automatically equate QA with testing. This is a convenient but imprecise simplification.
What testing means
Testing is the process of checking a product to find defects and establish whether the system behaves as expected.
In practical terms, testing includes opening a form, sending a request, checking the response, comparing expected and actual results, finding an error, and reporting a bug.
Testing asks: does the product work as it should?
For example, you enter a valid username and password in a login form, click the sign-in button, and check whether the user is signed in. That is testing.
What QC means
QC stands for Quality Control. It extends beyond manually executing tests but remains primarily focused on the product and identifying problems in it.
QC can include testing, reviewing requirements and test documentation, analyzing defects, and controlling quality before release.
Testing is a specific activity; QC is a broader set of activities that controls the quality of the result.
- →Testing is part of QC.
- →QC controls product quality.
What QA means
QA stands for Quality Assurance. It considers the product and the processes that produce quality.
QA asks: how can we organize the process to reduce errors?
It includes preventing problems early as well as finding defects after development.
QA can include clarifying requirements, improving development and testing processes, defining quality gates, introducing checklists and standards, analyzing defect causes, improving communication between analysts, developers, and QA, and working with quality metrics.
For example, if unclear requirements repeatedly cause bugs, a QA approach improves the requirements process to prevent recurrence, alongside detecting those bugs.
What verification means
Verification checks that the product is being built correctly according to its requirements and specifications.
Verification asks: are we building the product right?
Verification often involves reviewing artifacts before executing the system: requirements, designs, diagrams, documentation, test cases, and code.
- →Checking requirements for contradictions
- →Reviewing an API specification
- →Checking that test cases cover acceptance criteria
- →Code review
Verification often does not require running the application.
What validation means
Validation checks that the team has built the product users and the business actually need.
Validation asks: are we building the right product?
Validation more often involves actual system behavior: testing completed functionality, UAT, user scenarios, and comparison with business expectations.
For example, an implementation may satisfy every requirement while the payment journey remains difficult to use. From a validation perspective, the product may fail to meet the business need effectively.
A simple way to remember
- →Testing: check the product.
- →QC: control product quality.
- →QA: assure quality through processes.
- →Verification: are we building the product correctly?
- →Validation: are we building the right product?
Another common formulation is: Verification — “Are we building the product right?” Validation — “Are we building the right product?”
One scenario, five perspectives
Imagine a team implementing user registration.
- →Verification: review registration requirements and test cases.
- →Testing: enter valid and invalid data, check validation errors, and submit the form.
- →QC: organize quality checks for the whole feature before release and confirm the absence of critical defects.
- →Validation: assess whether registration is usable and meets the user's need.
- →QA: investigate recurring registration defects and improve the requirements process.
Common beginner mistakes
The first mistake is equating QA with testing. A tester may perform testing, but QA is a broader discipline.
The second is confusing verification and validation. Verification concerns requirements compliance; validation concerns meeting user and business needs.
The third is assuming quality is created only during testing. The earlier a team considers quality, the less expensive errors are to fix.
Conclusion
Testing finds product problems; QC controls product quality; QA establishes processes that help produce a quality product; verification checks implementation against requirements; validation checks whether the result meets user and business needs.
This is foundational knowledge for a new QA engineer. It matters in interviews and daily work: precise terminology makes it easier to communicate with your team and explain your role.