quality-metrics
Quality Metrics
<default_to_action> When measuring quality or building dashboards:
- MEASURE outcomes (bug escape rate, MTTD) not activities (test count)
- AVOID vanity metrics: 100% coverage means nothing if tests don't catch bugs
- SET thresholds that drive behavior (quality gates block bad code)
- TREND over time: Direction matters more than absolute numbers </default_to_action>
Quick Reference Card
When to Use
- Building quality dashboards
- Defining quality gates
- Evaluating testing effectiveness
- Justifying quality investments
Quality Gate Thresholds
More from proffesor-for-testing/agentic-qe
code-review-quality
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.
1.2Kapi-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
404compatibility-testing
Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.
381regression-testing
Strategic regression testing with test selection, impact analysis, and continuous regression management. Use when verifying fixes don't break existing functionality, planning regression suites, or optimizing test execution for faster feedback.
213test-automation-strategy
Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.
183technical-writing
Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
127