Stop 01 · QA & Software Testing FoundationsTopics · 2/9

QA vs Testing vs Quality Assurance vs Quality Control

Part of the QA Testing Roadmap

In short

People use QA, QC and testing as if they mean the same thing. They don't, and knowing the difference makes you sound sharp in interviews and plan work better.

Testing is the specific activity of executing test cases; QA is the broader discipline of preventing defects through process; Quality Control is checking the output for defects — terms often used loosely and interchangeably in practice.

The purple blob inspects a stack of rotis on a hostel mess counter with a checklist in hand.

Think of it like this

The hostel mess

The mess committee sets rules: fresh vegetables, clean utensils, a fixed menu. That's quality assurance. Someone checks each batch of rotis before serving. That's quality control. Actually tasting one roti is testing.

Watch it happen

How the three fit together

Quality
QA: process
QC: product
Reviews
Standards
Testing
Inspections

1/4Quality is the goal: software that does what users need without nasty surprises.

The big ideas

What you need to know

QA is about the process

QA asks 'how do we build things so fewer bugs happen?' Think code reviews, templates, definitions of done.

QC is about the product

QC asks 'is this particular build good?' It happens after something is made and looks for defects.

Testing is an activity

Testing means executing the software with specific inputs and checking the outputs. It is part of QC.

Job titles blur it all

A 'QA Engineer' job usually involves all three. Companies use the title loosely, so read the job description.

Save yourself the pain

Common mistakes

Oops

Saying QA and testing are the same thing.

Do this instead

Testing finds defects in a product. QA improves the way the team works so fewer defects are created.

Oops

Thinking quality starts only when the build reaches the tester.

Do this instead

Quality starts with clear requirements and good process. Testing at the end can only catch what slipped through.

Your mission

Sort the activities

~15 min

Quick check

Your team adds a rule that every pull request needs one reviewer before merging. Which is this?

Go deeper

  1. 1Learn the formal distinction between these terms, even though real job titles blend them.
  2. 2Notice how 'QA Engineer' job postings actually describe a mix of all these activities.
  3. 3Understand this vocabulary mostly matters for interviews and formal process documentation.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge