What Is Quality Management?

Key points

• Quality management is the set of activities that confirm a system works correctly according to its requirements and can be used with confidence.
• Starting from "test planning," you gradually widen the scope of verification: "unit test" → "integration test" → "comprehensive test" → "system test" → "UAT."
• The earlier a defect is found, the cheaper it is to fix.

?

Teacher Pochi uses services like this every day, too

📦 Online shopping 📱 Using apps 🏦 Online banking

📋Test PlanningBefore a new service launches, what gets checked, in what order, to make sure it actually works? 🔩Unit TestIs each tiny feature in an app checked individually to make sure it works? 🔗Integration TestSearching, adding to cart, checking out — how does that whole chain of steps get confirmed to work together? 🧩Comprehensive TestHow do they confirm the whole system behaves as expected when you use it start to finish? 🖥️System TestHow do they check ahead of time that things won't slow down even when lots of people use it at once, in a production-like environment? 🙋UATIs there a step, right before release, where a real user gets to say "yes, this works for me"?

What quality management actually means

Quality management is the ongoing set of activities that confirm whether a system you've built "works correctly according to its requirements" and "can be used with confidence" — and fixes any problems that turn up.

It doesn't just mean "running tests." It also includes deciding in advance what to check, when, and how — the "test plan" — so the term covers the whole effort of building quality in, not just the act of testing itself.

Teacher Pochi's hintIt's similar to the quality inspection a factory runs before shipping a product. Rather than looking only at the finished item, inspectors check parts, check the assembled unit, and do a final check before shipment — catching defective goods before they ever reach the customer.

The earlier a defect is found, the better

Even the same defect costs more to fix the later it's discovered. Fixing a single piece of code is a very different problem from having to deal with it after release, with real users caught in the middle.

That's exactly why it matters to build up testing in small units from the earliest stages of development.

The overall shape of the test process

Quality management typically proceeds in the following flow, starting with narrow-scope tests and gradually widening what's being checked.

We'll explain what each of these means in the following slides and in their own dedicated topics.

The V-model: design and testing side by side

Each test phase corresponds to something decided earlier, during design and requirements. The idea of mapping out this correspondence is called the "V-model."

Teacher Pochi's hintThink of it like the relationship between a recipe (design) and taste-testing (testing). Prepping each individual ingredient (program design) is confirmed by tasting as you go (unit test), while the finished, plated dish (requirements definition) is confirmed when a guest actually eats it (UAT).

The role of test planning

Test planning is the step where you decide, before testing actually begins, "what," "when," "who," and "how" to verify. Start testing without a plan and you end up with gaps in coverage or not enough time to finish.

See the dedicated "Test Planning" topic for details.

Unit test and integration test

A unit test confirms that the smallest unit of a program (a function or method, for example) works correctly. An integration test confirms that those units work correctly when combined.

In short: unit tests guarantee each individual part works, and integration tests check the "seams" where parts connect.

See the dedicated "Unit Test" and "Integration Test" topics for details.

Comprehensive test, system test, and UAT compared

A comprehensive test runs through the whole system to verify it behaves according to requirements, while a system test verifies non-functional requirements too — such as performance and security — in an environment equivalent to production. In practice, the two terms are sometimes used almost interchangeably.

UAT is the final check by the client or actual end users to confirm the system works for their business — the last gate in quality management.

See the dedicated "Comprehensive Test," "System Test," and "UAT" topics for details.

Summary

Quality management is the series of activities that, based on a test plan, widen the scope of verification step by step: unit test → integration test → comprehensive test → system test → UAT. Finding defects early and in small units keeps fix costs down.

You can learn more about each phase in the dedicated topics below.

Related topics:

• Test Planning
• Unit Test
• Integration Test
• Comprehensive Test
• System Test
• UAT

🏠 Back to top