Risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, or establishing release criteria.
QA Testing Strategy (Jan 2026) Risk-based quality engineering strategy for modern software delivery. Core references: curated links in data/sources.json (SLOs/error budgets, contracts, E2E, OpenTelemetry). Start with references/operational-playbook.md for a compact, navigable overview. Scope Create or update a risk-based test strategy (what to test, where, and why) Define quality gates and release criteria (merge vs deploy) Select the smallest effective layer (unit → integration → contract → E2E) Make failures diagnosable (artifacts, logs/traces, ownership) Operationalize reliability (flake SLO, quarantines, suite budgets) Use Instead
don't have the plugin yet? install it then click "run inline in claude" again.