Testing Platform

One master QA skill with modular sections for enterprise-grade testing decisions.

Scope

Use this skill as the single control plane for testing work:

• test strategy and architecture

• functional and non-functional planning

• test automation and CI gating

• test infrastructure and environment readiness

• QA governance and evidence quality

• quality metrics and release risk decisions

Navigation Rule

Do not load every reference file by default. Start with references/00-navigation.md , then open only the section that matches the user request.

Section Map

• Navigation and routing:

• references/00-navigation.md

• Strategy and architecture:

• references/01-strategy-architecture.md

• Functional testing:

• references/02-functional.md

• Non-functional testing:

• references/03-non-functional.md

• Automation architecture:

• references/04-automation.md

• Infrastructure and environments:

• references/05-infrastructure.md

• Governance and controls:

• references/06-governance.md

• Metrics and quality signals:

• references/07-metrics.md

• Risk management:

• references/08-risk-management.md

• Capability model and maturity:

• references/09-capability-model.md

SDLC Execution Flow

• Discovery:

• define quality goals, critical business flows, and constraints

• Planning:

• build risk model, select test scope by risk and change impact

• Build and integration:

• apply functional and non-functional plans, wire automation into CI gates

• Pre-release:

• evaluate governance gates, readiness evidence, and release risk

• Production feedback:

• monitor metrics, defect leakage, and incident patterns

• feed findings back into risk and strategy modules

Dependency Model

Layer 0 (fundamental):

• strategy and architecture

• risk management

Layer 1 (execution core):

• functional testing

• non-functional testing

Layer 2 (platform and acceleration):

• automation

• infrastructure

Layer 3 (business control):

• governance

• metrics

Feedback loop:

• metrics -> risk reprioritization -> strategy update -> coverage and gate updates

Capability Policy

Must-have core capabilities:

• test case generation

• risk-based prioritization

• regression impact analysis

• CI and CD integration logic

• baseline non-functional checks

• defect triage and release recommendation

Next maturity capabilities:

• observability feedback loop

• performance profiling

• security scanning orchestration

• auto-refactoring support for test suite health

Output Contract

When responding on testing work, return:

• Scope and assumptions.

• Risk profile and prioritization.

• Proposed test architecture and coverage.

• Gate plan for CI and release.

• Metrics and decision signals.

• Next actions in order.

Non-Negotiable Rules

• Do not propose 100 percent exhaustive testing; prioritize by risk and impact.

• Do not separate test strategy from release and observability feedback loops.

• Do not approve release decisions without evidence-backed metrics.

• Do not add advanced automation before stabilizing fundamental strategy and risk controls.

References

• Navigation

• Strategy and Architecture

• Functional Testing

• Non-Functional Testing

• Automation

• Infrastructure

• Governance

• Metrics

• Risk Management

• Capability Model