skills.rest
matthew-bram
matthew-bramCOMMUNITY
Explore all skills by this author →
GitHub

test-quality-enforcer

Enforce two-phase testing and coverage thresholds on code commits.

Updated Dec 4, 2025
Search Tags:#testing#quality assurance#ci/cd#code coverage#regression testing#bdd
One-click install
npx skills add https://github.com/matthew-bram/enterprise-confluent-test-probe --skill test-quality-enforcer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-quality-enforcer
Source: https://github.com/matthew-bram/enterprise-confluent-test-probe/tree/main/.claude/skills/test-quality-enforcer
Command: npx skills add https://github.com/matthew-bram/enterprise-confluent-test-probe --skill test-quality-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces rigorous test quality standards by implementing a two-phase testing strategy, ensuring that code is thoroughly tested for both module-specific stability and overall project regression before deployment.

Core Features & Use Cases

  • Two-Phase Testing: Executes fast module-focused tests followed by comprehensive project-wide regression tests.
  • Hard Block Enforcement: Prevents progression if tests fail, errors occur, or coverage thresholds are not met.
  • Coverage Thresholds: Enforces minimum coverage (70% overall, 85% actors, 80% business logic).
  • Undefined Step Guidance: Automatically detects and helps implement missing Cucumber steps.
  • Use Case: When a developer commits code, this Skill automatically runs their module's tests. If they pass, it proceeds to run all project tests. If any test fails or coverage is low, it blocks the process and provides specific feedback.

Quick Start

Run the test-quality-enforcer skill to verify all tests pass and coverage meets the required thresholds.

Frequently Asked Questions about test-quality-enforcer

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

FAQPage Schema
How do I enforce zero-tolerance code coverage thresholds in my CI/CD pipeline?▼

This Skill enforces zero-tolerance coverage by blocking builds that fall below specific thresholds: 70% overall coverage, 85% actor coverage, and 80% business logic coverage.

What is a two-phase regression testing strategy and how does it work?▼

A two-phase regression testing strategy runs fast module-focused tests first to verify specific component stability, then executes comprehensive project-wide regression tests to ensure overall build integrity before deployment.

How do I implement undefined Cucumber BDD steps automatically during testing?▼

When undefined Cucumber BDD steps are detected during test execution, the system automatically identifies the missing steps and provides guidance to implement them, ensuring continuous build integrity without manual intervention.

Can I block a deployment automatically if my unit tests fail or error out?▼

Yes, you can use hard block enforcement to prevent pipeline progression automatically if any tests fail, errors occur, or coverage thresholds are not met, providing specific feedback for fixes.

Does this testing strategy require any specific testing frameworks or dependencies to run?▼

No specific testing framework dependencies are required to implement this two-phase testing strategy, as it operates by orchestrating your existing test suites and analyzing coverage metrics directly.

Related Skills

Explore More Software Engineering Skills→
ShubhamManachekarShubhamManachekar

cicd-checkers

Enforce CI/CD phase gate rules and pytest suites for Phase 12 deployments.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
wuzinongwuzinong

behavior driven test

Transform user stories and acceptance criteria into executable Gherkin BDD scenarios.

Community
Advanced
blahami2blahami2

bug-fixer

Diagnose software bugs by writing automated regression tests before fixing code.

Community
Advanced