QA vs QC vs Testing: Key Differences

QA, QC, and testing are often used interchangeably, but they refer to different aspects of quality. Understanding the distinctions helps you communicate clearly and plan your work as a QA professional.

Quality Assurance (QA)

QA is process-oriented. It focuses on how work is done: standards, processes, and practices that prevent defects. Examples include test planning, review processes, definition of done, and continuous improvement of the testing approach. QA aims to improve the system so that quality is built in.

Quality Control (QC)

QC is product-oriented. It focuses on what is produced: checking deliverables against requirements and standards. Executing test cases, finding bugs, and validating builds are QC activities. QC finds defects; QA helps prevent them.

Testing

Testing is the activity of checking software behavior. It is part of both QA and QC: test design and planning support QA; test execution and defect reporting support QC. In practice, "QA" and "testing" are often used to mean the same team or role.

How they work together

• QA: Define and improve processes (e.g. test strategy, automation standards).
• QC: Run tests and verify the product (e.g. run regression, log bugs).
• Testing: The concrete work of designing and executing tests.

Summary

• QA = process and prevention; QC = product and detection; testing = the activity of checking software.
• In many teams, "QA" covers both process and execution; knowing the terms helps when reading job descriptions and standards.