Define QA test strategies, acceptance criteria, and CI quality gates.
npx skills add https://github.com/wesleyosantos91/multi-agents --skill qa-process
Please help me install this Agent Skill. Skill: qa-process Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/qa-process Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill qa-process
QA and quality engineering processes often become inconsistent or incomplete, leading to regressions, uncovered edge cases, and releases that fail under real-world conditions.
Use the qa-process skill to design a complete QA plan for a specific feature by providing its scope and risk level (normal vs critical) and then asking for acceptance criteria, edge cases to cover, and the recommended CI quality gates.
High-intent search queries and answers about installing and using this skill.
A test strategy defines testing allocation across unit, integration, and E2E layers based on risk and user-critical paths. It establishes clear acceptance criteria, regression planning, and CI quality gates to ensure release readiness and prevent regressions.
Edge case coverage in software QA requires a systematic checklist analyzing data, state, dependency, and HTTP boundary failures. This includes validating concurrency, retries, idempotency, and malformed inputs to ensure features perform reliably under real-world conditions.
CI quality gates for regression testing specify automated tests to run on every PR alongside measurable coverage thresholds. They enforce defect prevention standards before merge, ensuring code meets baseline quality requirements and critical paths remain stable.
A structured quality reporting template is needed when assessing release readiness to document test coverage, edge case validation, and remaining risks. It provides a standardized format for capturing quality metrics and supporting final go/no-go release decisions.
Acceptance criteria establish actionable release gates for both normal and critical features. They include specific security and failure-mode validation requirements for critical paths, ensuring comprehensive Definition of Done across varying risk levels.
Test strategy planning applies to unit, integration, and E2E testing layers. It allocates testing distribution based on risk analysis and user-critical paths, ensuring balanced coverage across the test pyramid for comprehensive software validation.
hujianbestDefine project scope and risk during HarnessFlow's Frame stage.
gopherguidesIdentify Go test coverage gaps and generate test stubs.
magnus919Standardize QA strategies for unit, integration, and E2E testing.
BoraPerusicGenerate failing test templates with edge cases and error paths.
