Quality Basics for Quality Assurance (QA)s
Quality basics are the ideas every tester starts from: what testing can and cannot prove, the test pyramid, and how testing fits the software development life cycle. It also covers working in Agile teams, where testing happens continuously inside each sprint instead of as a late phase.
Stage: Testing Fundamentals · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in Quality Basics
- State the seven classic testing principles in your own words
- Explain the test pyramid and why most tests should be small and fast
- Distinguish verification from validation with an example
- Describe where testers contribute in each Agile ceremony
- Separate functional, non-functional, smoke and regression testing
- Explain why exhaustive testing is impossible
Quality Basics interview questions
What is the difference between QA and QC?
QA is process-oriented and aims to prevent defects through standards, reviews and good practice. QC is product-oriented and finds defects by inspecting or testing the built product. Testing is a QC activity that sits inside the wider QA effort.
Why does the test pyramid put unit tests at the bottom?
Unit tests are cheap, fast and precise, so a team can run thousands on every commit. UI tests are slower, brittle and costly to maintain, so they go at the top in small numbers. The shape keeps feedback quick and failures easy to locate.
Where Quality Basics fits in the Quality Assurance (QA) roadmap
Quality Basics belongs to the Testing Fundamentals stage (beginner level), which takes about 7 hours. Think like a tester.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap