QA and Testing are related but different. QA prevents bugs; Testing finds bugs.
These terms are often used interchangeably, but they're fundamentally different. QA is about building quality in (prevention). Testing is about verifying quality out (detection). A complete quality strategy uses both.
E-commerce payment bug
Code review finds: Payment code missing input validation. Bug never reaches production.
QA's code review missed it. Tester finds: Payment accepts negative amounts. Reports bug.
Dynamic activity - executing software to find defects
Product quality - Is the product good?
Detection-oriented - Finding what's wrong
Typically: After development (though in Agile it's continuous)
Static activity - preventing defects through process improvement
Process quality - Did we follow good practices?
Prevention-oriented - Ensuring things go right from start
Throughout development - From requirements to deployment
| Aspect | Testing | Qa |
|---|---|---|
| Goal | Find defects (detective) | Prevent defects (preventive) |
| Focus | Product - Is software correct? | Process - Is development correct? |
| Activity Type | Dynamic - Execute and test | Static - Review and improve |
| When Done | Mostly after development | Throughout development |
| Cost of Action | High - Finding bugs late is expensive | Low - Prevention is cheaper than cure |
| Example | Run test case, find crash in checkout | Enforce code review before checkout code is written |
Building a House
QA = Have good architectural plans, follow building codes, hire qualified workers, review blueprints, inspect during construction
Testing = After house is built, inspect walls for cracks, check plumbing works, test electrical, verify quality
QA prevents problems. Testing finds any problems QA missed.
A bug reaches production where users can access other users' account data. How would QA have prevented this vs how would Testing have caught it?
🎯 QA prevents (better), Testing finds (necessary backup). Best strategy = Strong QA process + comprehensive Testing.
This distinction is a classic conceptual interview question. Interviewers test if candidates understand the relationship and purpose of both.