Practice Note: How Testing Became Quality Management Without Leaving Testing Behind

Testing has changed considerably over the years.

What once focused primarily on evaluating software products has expanded into test automation, quality assurance, quality engineering, process improvement, and increasingly organizational capability development.

We have moved upstream, becoming involved in requirements, architecture, development practices, and organizational ways of working.

Yet we still tend to describe much of this work as testing.

Perhaps we have expanded the discipline without reconsidering what the discipline has become.

Following Quality Upstream

Testing provides information about products.

When something doesn’t work as expected, testing helps us discover it, investigate it, and understand its consequences.

But many problems discovered through testing originate elsewhere.

Ambiguous requirements, architectural decisions, inadequate development practices, or insufficient organizational capabilities may all become visible through testing.

Improving testing alone does not necessarily address these problems.

So we started moving upstream.

We became involved in requirements reviews, development practices, risk management, process improvement, and eventually organizational assessments.

The underlying motivation remained the same: improving our ability to achieve quality.

But the subject of our attention gradually changed.

We were no longer concerned only with evaluating products. We were increasingly concerned with understanding and improving the organizational mechanisms that produce them.

From Testing to Quality Management

This development introduced a collection of overlapping concepts.

Quality Assurance, Quality Control, Quality Engineering, Test Management, and Quality Management are frequently used in ways that make their responsibilities difficult to distinguish.

Perhaps the problem is not primarily terminology.

Perhaps we have been trying to accommodate an increasingly broad set of responsibilities within a discipline originally organized around testing.

A useful distinction might be:

• Testing investigates products and provides evidence about their behaviour and characteristics.
• Quality Control evaluates whether products satisfy relevant quality expectations.
• Quality Assurance provides confidence that the ways of working used to achieve quality are adequate.
• Quality Engineering develops and applies engineering practices that help achieve quality.
• Quality Management provides the organizational mechanisms for directing, evaluating, and improving the ability to achieve quality.

These are not necessarily competing disciplines.

They address different aspects of the same challenge.

And testing remains an essential part of that challenge.

Assessing More Than Products

Organizations routinely evaluate their products.

They test software, inspect deliverables, monitor performance, and investigate defects.

But how systematically do they evaluate the organizational capabilities responsible for producing those products?

When testing repeatedly reveals poor requirements, do we assess the organization’s requirements engineering capability?

When defects originate in architectural decisions, do we examine the architecture capability?

When problems recur across projects, do we investigate the organizational mechanisms that should enable learning and improvement?

Often, we address the immediate problem without systematically evaluating the capability behind it.

This suggests an interesting extension of Quality Management.

Just as product assessment provides evidence about products, capability assessment could provide evidence about the organization’s ability to achieve intended outcomes.

And just as product development responds to findings about products, capability development could respond to findings about organizational capabilities.

Quality Management would then concern itself not only with whether quality is achieved, but also with whether the organization has the capabilities required to achieve it repeatedly.

Without Leaving Testing Behind

None of this makes testing less important.

Testing remains one of our most valuable sources of evidence about whether products behave as intended.

It also provides an important perspective on the consequences of decisions made elsewhere.

But testing cannot compensate indefinitely for weaknesses throughout the organization.

Nor should it be expected to.

Moving upstream does not mean abandoning testing. It means recognizing that the information testing provides can lead us toward questions that testing alone cannot answer.

And perhaps that is how testing gradually led us toward Quality Management.

Not because testing became something else, but because understanding quality required us to look beyond testing.

Quality is created throughout the organization. Quality Management makes that creation intentional, coordinated, and improvable.