Item: qa-testing-strategy
Rating: 5.3
Author: Implexa

qa-testing-strategy

Risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, or establishing release criteria.

installs

stars

karma

SkillRank score ↗

5.3/ 10

evaluated by implexa, claude-haiku-4-5 · 2026-06-21

qa-testing-strategy outlines a risk-based approach to test coverage and release gates, referencing operational playbooks and error budgets but lacks concrete step-by-step procedures and explicit failure recovery patterns.

structure

4.0

trigger phrases

4.0

procedure

5.0

edge cases

4.0

documentation

6.0

strengths

SKILL.md

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.

qa-testing-strategy

SKILL.md

related skills