Professional Expression 03 · Working Practice v0.1

Human-Centred Quality in Practice: The Test Architect

Close to systems, systemic relationships, testability and longer-horizon quality strategy. This is a proposition to put into practice, not an authoritative definition.

Explore the expressionCompare the roles

Working professional expression

A working expression of Human-Centred Quality through the role of a Test Architect. It is offered as a strategic and systemic lens to be used, challenged and improved through practice.

Same Practices. Different professional vantage point.

Observe → Interpret → Understand → Judge → Improve → Steward remains common. The question is how each Practice is expressed when professional responsibility and proximity to evidence change.

Test Architect

The six Practices through this lens

Observe

Look beyond individual test outcomes for systemic behaviour, dependencies, constraints, recurring failure patterns, gaps in observability or testability, and places where architecture makes quality difficult to establish.

Make it visible: Record significant systemic observations and reference the technical, operational, test or architectural evidence from which they arose.

Interpret

Explore what observations might reveal about architecture, testability, resilience, integration, data, environments or the adequacy of the quality approach. Preserve competing explanations when evidence is incomplete.

Make it visible: Keep architectural interpretations distinguishable from observations; record assumptions, alternatives and uncertainty.

Understand

Connect evidence across components, journeys, environments, quality characteristics and disciplines to develop a coherent explanation of systemic quality behaviour.

Make it visible: Record the current systemic understanding, important relationships and what remains unknown or untested.

Judge

Determine what the developing understanding means for test architecture, quality risk, investment, technical choices and the evidence required for responsible decisions.

Make it visible: Preserve significant architectural recommendations, rationale, consequences, assumptions and accepted uncertainty.

Improve

Change the conditions under which quality can be understood: testability, observability, automation architecture, environments, data, interfaces, controls or testing strategy.

Make it visible: Record the intended architectural improvement and later evidence of whether it improved the ability to understand or assure quality.

Steward

Preserve why architectural choices were made, reusable patterns, failed approaches, systemic risks and lessons that should influence future quality architecture.

Make it visible: Preserve reusable architectural knowledge with provenance and connect it to the evidence from which it developed.

Worked glimpse

What this might look like in practice

Across four services, most intermittent integration failures cluster where asynchronous processing crosses the same messaging infrastructure. One interpretation is an architectural weakness; another is test-environment instability. Evidence supports both, while also revealing insufficient message-state visibility. The judgement is that adding test volume alone will not increase confidence proportionately. Improvement introduces correlation identifiers, cross-service observability and recovery scenarios. Stewardship preserves the pattern that credible testing of asynchronous recovery depends upon cross-service observability.

Use it. Challenge it. Tell us what practice reveals.

This v0.1 exists to stimulate contribution. What is missing? What is over-stated? What behaves differently in your environment?

Contribute from experience Compare professional expressions