Types of testing — a working taxonomy for QA engineers

Why this matters

Saying 'we did testing' is like saying 'we ate food' — technically true, completely uninformative. A QA engineer needs a working vocabulary of testing types to design a test strategy, communicate coverage to stakeholders, and identify gaps. The taxonomy splits along several axes: by scope (unit → integration → system → acceptance), by objective (functional vs non-functional), by execution method (manual vs automated), and by timing (smoke before regression, regression before exploratory). Knowing which type is needed when — and which you're missing — is the core skill of test planning.

Demo

Testing type vocabulary lets QA engineers communicate coverage gaps precisely instead of vaguely. Saying 'we're missing regression coverage for the checkout module' is actionable; 'we haven't tested enough' is not. Each type in this taxonomy targets a distinct failure mode — unit tests catch logic errors, smoke tests catch deploy failures, security tests catch vulnerability classes that functional tests never reach.

Try it yourself

1. Filter taxonomy to only automated tests: [t for t in taxonomy if t.automated]. What percentage of the total is automated? For the remaining manual ones, write a one-line explanation of why they're hard to automate.
2. Add a cost: str field with values 'low', 'medium', 'high'. Assign costs (unit tests = low, performance = high, security = high). Sort by cost. This is the data behind the 'test pyramid' — cheap-to-run tests at the bottom, expensive at the top.
3. Design a minimal test strategy for a new e-commerce checkout feature: list which test types you'd use, who runs each, and the order. What would you skip if you had 2 days instead of 2 weeks?
4. Research the 'testing trophy' (Kent C. Dodds) vs the 'testing pyramid' (Mike Cohn). What's the key difference in where they suggest investing testing effort? Which model does your current team follow?

Prompt your AI

Use these three in order. Each builds on the one before.

1. Basics & terminology

In one paragraph, explain the difference between smoke testing and regression testing. When would you run each, and what happens if the smoke test fails?

2. Why it works (the mechanism)

Walk me through how you'd design a test strategy for a new payment feature: which test types in which order, what coverage each provides, and what risk is left uncovered by each type.

3. Advanced — application & what's next

A PM asks you to cut testing time in half for the upcoming release. Walk me through how you'd decide which test types to prioritize vs skip, how you'd communicate the residual risk, and how you'd measure whether the decision was correct after the fact.

References

• ISTQB Foundation Level Syllabus