Lesson 1 of 104 min read
What is QA and why companies pay for it
Quality Assurance (QA) makes sure software works the way users and the business expect, before real customers find the problems.
Key takeaways
- 1QA is about preventing problems; testing is the activity of finding them.
- 2A bug found in production can cost far more to fix than one found during development.
- 3Testers think like users, like attackers and like the business all at once.
Real example: a food delivery app
A developer builds a 'Apply coupon' button. A tester checks: a valid coupon, an expired coupon, a coupon used twice, a coupon on an empty cart, and a coupon that makes the total negative. The last case is a real bug that would lose the company money on every order.
Go deeper
Expert notes beyond the basics
- 01
QA, QC and testing are not the same thing
Quality Assurance is about the process: agreeing on requirements, reviewing designs, setting standards so fewer bugs are created. Quality Control checks the product itself against those standards. Testing is the hands-on part of QC where you run the software and compare what happens with what should happen. In everyday job titles the three words get mixed, but knowing the difference makes you sound confident in interviews.
- 02
Why a company pays for testers
Every release carries risk: lost sales if checkout breaks, legal trouble if personal data leaks, bad reviews if the app crashes. Testers reduce that risk by giving the team fast, honest information about quality. You are not paid to find the most bugs; you are paid to help the team ship with confidence.
- 03
The cost of a late bug
A wrong requirement caught in a meeting costs a short conversation. The same mistake caught after release can mean an emergency fix, a re-release, support tickets and refunds. This is why good testers get involved early, reading requirements and asking questions before any code is written. This idea is often called shift-left testing.
Common mistakes to avoid
- - Saying the tester's job is to make the software bug-free. No amount of testing proves there are no bugs.
- - Thinking QA only starts after development is finished.
- - Treating developers as opponents instead of teammates working on the same goal.
Try it yourself
A food delivery app has an 'Apply coupon' button on the cart screen. Write 6 test ideas (not full test cases, just short bullet ideas) that show you are thinking like a tester, not just a user.
Write your answer on paper or in a sheet first, then compare.
Interview questions
How to answer like a confident QA engineer
- Q1
What is the difference between QA and testing?
Model answer
QA is the process-level work that prevents defects (reviews, standards, good requirements). Testing is executing the product to find defects. Testing is one part of QA.
- Q2
What is the difference between QA and QC?
Model answer
QA is process-focused and preventive: it improves how software is built so fewer defects appear. QC is product-focused and detective: it checks the finished product to find defects. Testing is one QC activity.
- Q3
Can testing prove software has no bugs?
Model answer
No. Testing can show bugs are present, not that they are absent. That is why we test based on risk, focusing effort where failures would hurt users or the business most.
- Q4
What is shift-left testing?
Model answer
Moving testing activities earlier in the project, such as reviewing requirements, joining design discussions and writing tests alongside code, so defects are found when they are cheapest to fix.
Knowledge check
+5 points
Which of these is the best description of a tester's job?