QA StepsLog in

QA vs QC vs testing: what is the difference?

Quality assurance (QA) is work on the process: how a team writes, reviews, builds and checks its work, so that fewer defects get made in the first place. It prevents, and it is the whole team's job. Quality control (QC) is work on the product: it evaluates what has been built and finds what is wrong with it. Testing is a major form of quality control. QA and QC are both parts of quality management. The fix itself, finding the cause in the code and changing it, is a third thing called debugging, usually done by developers. Testing is not the same as QA, even though many job ads call testers "QA engineers".

3 kinds of work
prevent, detect, fix
2 parts
of quality management: QA and QC
The whole team
owns quality assurance
Arti, the QA Steps tutor, in a scene for the article "QA vs QC vs testing: what is the difference?"
The same topic as a short video lesson on the QA Steps YouTube channel.

Prevent, detect, fix: one week on one team

Shelf is the practice shop the author's courses use. In one week, its team did three things for the quality of the coupon feature. Read them before the labels.

The first move changes how the team works, so the next story is less likely to have the same gap. That is quality assurance: aimed at the process, and preventive. The second move looks at the product and finds what is wrong with it. That is testing, a form of quality control. The third move changes the code to remove the cause. That is debugging.

The three feed each other. The USD 0.00 from the tester gets one defect fixed, and it is also the kind of finding that makes a team add a rule like the first one. Testing uses its results to get defects fixed; QA uses the same results to improve the process.

Three moves, three kinds of work
1. The team agrees that every story lists its limits
   before work starts.
   -> prevents: quality assurance (process, whole team)

2. A tester applies SAVE25 twice in the cart and
   records the total: USD 0.00.
   -> detects: testing, a form of quality control (product)

3. A developer removes the line that applied the
   discount a second time.
   -> fixes: debugging (code, usually a developer)
Diagram: Prevent, detect, fix: one week on one team

Is testing the same as QA?

No, and the confusion has a simple source. Job ads say "QA engineer" when they mean a tester, so it is easy to believe that QA means the testers and that the testers guarantee quality. A developer pushes a quick fix and writes on the ticket: "QA will make sure it's fine." Who is responsible for the quality of that fix? The whole team. The story's author and the developer build its quality; the tester's checks show what is still wrong. A tester detects and informs.

In practice, many companies do not separate the three, and one tester does a bit of each. Starting out, you will mostly do testing and QC; QA work in the wider sense, such as changing how stories are written or reviewed, may come later. Know the difference anyway. It tells you what testing can take on and what it cannot.

An interviewer may draw nested circles: testing inside QC, QC inside QA. That picture comes from older training material, and the current foundation syllabus for testers does not use it. Do not argue about circles. Say that QA and QC are two parts of quality management, that testing is a major form of QC, and then sort any activity by what it does: prevents, detects or fixes.

Testing starts before the code

Here is a user story in full: "Customers can apply a coupon to their cart." A user story is a short note about what a user wants to do with the software. There is no screen yet and no code. Can you test it? Yes. Read it as a tester and the questions come at once. What happens with a second coupon? Can the same coupon be applied twice? What does the cart show if the coupon is worth more than the cart?

Reading and reviewing a story, a design or code without running it is static testing. Running the software and watching what it does is dynamic testing. Both are testing, both are quality control, and a problem found in a sentence is cheaper to fix than the same problem found in code.

Finding defects is one objective of testing, not the only one. Testing also evaluates work products like this story, checks the product against laws and contracts, gives the team information for decisions, and builds confidence: a cart checked with one coupon, two coupons and an expired one can be released with good reasons. "To find as many bugs as possible" is a weak interview answer to "what is testing for?"

From a mistake to a fix: error, defect, failure, debugging

Follow one incident. A sale is coming, and the coupon story is written in a rush. Its author forgets to say that a coupon applies once. The code applies the discount on every click of Apply. A customer clicks Apply twice, quickly, and the cart shows 0.00.

The forgotten rule is an error, a human mistake. The code that applies the coupon on every click is a defect, the flaw the error leaves in a work product. The 0.00 on screen is a failure, what someone sees when the defect runs. The rush before the sale is the root cause. Not every defect causes a failure every time: with one click, this cart looks perfect.

After a failure, the work splits along the same line as above. The tester detects and reports. The developer reproduces the failure, finds the defect and fixes it, which is debugging. Then the tester runs the same check again to confirm the fix and looks at whether anything nearby broke.

When every check passes, the tester still does not guarantee quality. Twelve cart checks pass, and a cart with SAVE25 applied twice has not been checked yet. "All tested, no bugs, safe to release" claims something testing cannot show. "The 12 cart checks passed; applying SAVE25 twice is not checked yet" gives the team real information. The product owner or a manager decides whether it ships.

Where to learn this

Questions and answers

What is the difference between QA and QC?

Quality assurance works on the process and prevents defects: rules, reviews, training, agreed ways of working. Quality control works on the product and evaluates it: it finds what is wrong with what was built. Testing is a major form of quality control.

Is testing the same as QA?

No. Testing checks the product and finds defects. QA improves the process so that fewer defects are made, and it is the whole team's job. Job titles often say "QA" for testers, and in many teams one tester does some of both.

Is QC part of QA, or is testing part of QA?

Older material drew nested circles, testing inside QC inside QA. The current foundation syllabus for testers does not. QA and QC are two parts of quality management, and testing is a major form of QC.

Who is responsible for quality, the testers?

The whole team. The people who write the stories and the code build quality in; testers detect what is still wrong and report it, so the team and the product owner can decide.

What is the difference between testing and debugging?

Testing shows failures, or finds defects directly when reviewing. Debugging reproduces the failure, finds its cause in the code and removes it. Debugging is usually a developer's work.

What are some examples of quality assurance activities?

A rule that every story lists its limits before work starts, a second reviewer for discount logic, a checklist for discount rules, and new team members learning the coupon rules before they change coupon code. Each one changes how the work is done before a mistake happens.

More guides

See the first course

The full outline of every course is available: you can see each lesson before you start.

All courses

Cookies keep you signed in. With your OK, one more remembers which link brought you here. Learn more