A Digital Consulting Plus methodology
English
← Full mapCurated public summary
Index
Handbook
01DCP Flow: what it is and why it exists02How DCP Flow works03How to start a project04Kai and working with AI agents04AKai operational capabilities05Institutional Prompt Cookbook06Solution Discovery explained for humans07Architecture, stack, and technology ecosystem07ATool & MCP Registry07BHostinger MCP for DCP websites and hosting08Quality Gates, QA, security, and evidence08AQuality profiles and testing strategy09Git, branches, PRs, and multi-agent work10Deploy, release, support, and operational evolution10AContainer First and standardized host operations10BPractical Container First demo11How DCP Flow evolves12Real cases and lessons learned13How to teach DCP Flow14Practical DCP Flow use cases15End-to-end playbooks: Web and Laravel
Entry 08A57%
57%12 / 21
Entry 08APUBLIC HANDBOOK

Quality profiles and testing strategy

How DCP Flow derives a Quality Profile from Delivery Mode, risk, lifecycle, and change surface to require proportional evidence.

Source & authority

Public explanation

PUBLIC HANDBOOK
Based on
Human Handbook 08A — Quality profiles and testing strategy
Related normative sources
  • NORMATIVE SOURCEStandard · QA & Testing
  • NORMATIVE SOURCEStandard · Quality Gates
Authority
Public explanation — NON-NORMATIVE
Summary

How DCP Flow derives a Quality Profile from Delivery Mode, risk, lifecycle, and change surface to require proportional evidence.

DCP Flow does not apply one universal QA suite to every project. It derives a Quality Profile from Delivery Mode, risk, lifecycle, and affected surface so evidence stays sufficient without turning quality into ceremony.

Quality Profile follows the real solution type

ADOPT, CONFIGURE, INTEGRATE, EXTEND, and BUILD require different validation focus. ERP configuration needs process, permissions, data, and UAT; integrations need contracts, retries, idempotency, and recovery; custom applications need code and non-functional checks proportional to risk.

Key points
  • Delivery Mode changes QA focus.
  • One project may combine several modes.
  • Diff size does not define risk.
  • CONFIGURE still requires evidence.

Testing scales with the lifecycle

Working branches prioritize fast feedback; PRs to dev widen integration and affected regression; integrated dev validates system coherence and Golden Flows; release candidates concentrate release evidence; production verifies smoke, health, and observability.

Key points
  • Impact-based regression.
  • Golden Flows protect end-to-end value.
  • NOT RUN never means PASS.
  • Define capabilities before choosing tools.
Contextual glossary＋
Quality Profile

Validation profile derived from Delivery Mode, risk, lifecycle, and change surface; defines the QA/testing capabilities and evidence required.

Delivery Mode

Solution path —ADOPT, CONFIGURE, INTEGRATE, EXTEND, or BUILD— describing how a capability is delivered and shaping its validation profile.

Golden Flow

Critical end-to-end journey that must work and produce verifiable evidence.

Quality Gate

Checkpoint where evidence determines whether work may progress.

Pre-Merge Audit

Pre-integration review for conflicts, regressions, known debt, and missing evidence.