Skip to content

QA / Quality lead perspective ​

Lens: Quality enforced by automation — test pyramid, static analysis, CI gates, and production feedback loops. No manual test execution phase.

Phase by phase ​

PhaseYour jobKey artifactsGuides & SOPs
PlanClarify testability of acceptance criteriaTestable AC in storySOP-001
DefineReview BDD; contract test strategyGherkin + OpenAPISpec-driven dev
BuildReview AI-generated test design in PRsTest quality in reviewAutomated testing
VerifyOwn CI quality gates policyGate thresholds by tierLinters · SOP-005
ReleaseConfirm staging synthetics greenSmoke evidenceSOP-006
OperateMonitor-as-QA alerts; escaped defect trackingIncident → test linkObservability as QA
LearnMandate regression tests Sev-1/2Merged regression PRSOP-008

What QA does not do in this model ​

  • Manual regression passes or UAT script execution
  • Sign-off after running test cases by hand

What QA does do ​

  • Define and tune automated gate policy
  • Meta-review test design in PRs
  • Track escaped defects and close the loop to CI
  • Partner with SRE on monitoring-as-QA patterns

Deep dive: QA & guardrails

Pitfalls (QA view) ​

PitfallMitigation
Reintroducing manual QA "just in case"Automate the check instead
AI tests from implementationGenerate from OpenAPI
Weak mutation scores on T1Tier-based mutation floor
Ignoring prod alerts as "ops only"Escaped defect process

← All roles

Reference template only — no production code. Adapt in your own project.