qa-metrics

Define QA metrics and action thresholds for test health.

2|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill qa-metrics-rabbicse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-metrics
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/qa-metrics
Command: npx skills add https://github.com/rabbicse/go-projects --skill qa-metrics-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns scattered test results, coverage numbers, and production defect signals into actionable QA metrics so teams can spot quality problems early and decide what to fix next.

Core Features & Use Cases

  • Defines the core quality metrics teams should track, including code coverage, flakiness rate, defect escape rate, MTTR, suite duration, automation ROI, and quality gates.
  • Maps each metric to a formula, a realistic target by company stage, an owner, and a concrete action when the metric goes red.
  • Helps teams choose the right dashboard view for engineers, leadership, and sprint retrospectives without drowning in vanity metrics.
  • Use it when you need to diagnose flaky tests, justify automation investment, set release quality gates, or build a metrics rollout plan for CI-driven quality tracking.

Quick Start

Ask me to define the QA metrics your team should track from your CI, coverage, and defect data, and I will return formulas, targets, owners, and red-state actions.

Frequently Asked Questions about qa-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What QA metrics should I track for test health in my CI pipeline?

QA metrics for test health include code coverage, flakiness rate, defect escape rate, MTTR, suite duration, and automation ROI. Tracking these across your CI pipeline helps spot quality problems early and determines what to fix next.

How do I calculate defect escape rate and set action thresholds?

Defect escape rate maps to a specific formula alongside a realistic target based on your company stage. It includes an assigned owner and a concrete red-state action to execute when the metric drops below acceptable quality gates.

How do I set quality gates for releases using coverage and flakiness data?

Setting release gates involves mapping metrics to specific formulas, assigning owners, and triggering automated red-state actions when thresholds are breached.

Can I use DORA-style quality reporting for CI-driven test tracking?

DORA-style quality reporting applies directly to CI-driven test tracking by integrating suite duration and MTTR metrics. It translates scattered test results and production defect signals into actionable dashboards for leadership and sprint retrospectives.

What is the best way to diagnose flaky tests using CI history?

Diagnosing flaky tests using CI history requires tracking the flakiness rate metric against defined action thresholds. The best approach applies specific red-state actions and ownership mappings to isolate and resolve unstable test behaviors.

How do I justify automation ROI to leadership without vanity metrics?

Justifying automation ROI requires mapping the metric to a formula, a realistic target by company stage, and an assigned owner. This approach filters out vanity metrics and provides concrete red-state actions for leadership dashboards and sprint retrospectives.