skills.rest
Unson-LLC
Unson-LLCOFFICIAL
Explore all skills by this author →
Website𝕏@AIBizNavigatorGitHub

test-strategy

Validate repository test suites against Brainbase's Test Pyramid distribution, coverage, and naming standards.

9|Updated Nov 22, 2025
Search Tags:#strategy#coverage#test#naming#CI#pyramid
One-click install
npx skills add https://github.com/Unson-LLC/brainbase --skill test-strategy-unson-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-strategy
Source: https://github.com/Unson-LLC/brainbase/tree/main/.claude/skills/test-strategy
Command: npx skills add https://github.com/Unson-LLC/brainbase --skill test-strategy-unson-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures Brainbase adheres to its Test Pyramid strategy by automatically validating test distributions (Unit/API/E2E), coverage thresholds, and naming conventions to uphold high-quality code.

Core Features & Use Cases

  • Phase 1: Pyramid Checker: verifies Unit/API/E2E distribution aligns with 80%/15%/5%.
  • Phase 2: Coverage Checker: confirms overall test coverage is at least 80% and identifies gaps.
  • Phase 3: Naming Checker: enforces readable, consistent test names (describe/it patterns).

Quick Start

Run the test-strategy skill to audit the repository's tests against the Pyramid, coverage, and naming standards, and report any deviations.

Frequently Asked Questions about test-strategy

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

FAQPage Schema
How do I enforce the test pyramid distribution across unit, API, and E2E tests?▼

To enforce the test pyramid distribution, the skill automatically validates that your repository-wide test suite satisfies an 80% Unit, 15% API, and 5% E2E ratio. It audits tests and reports any deviations from this strategy.

What is the required test coverage threshold to pass the audit?▼

The required test coverage threshold is 80% overall. The coverage checker confirms your repository meets this minimum and identifies specific coverage gaps where additional tests are needed.

How do I check if my test naming conventions follow describe and it patterns?▼

To check test naming conventions, run the skill to enforce readable, consistent test names using describe and it patterns. It validates your suite against standard naming requirements and reports deviations.

Can I validate test strategy across an entire repository or is it per-file?▼

You can validate test strategy across an entire repository. The skill applies to repository-wide test suites and workflows, auditing the full project context rather than isolated files.

What are the limitations of automated test pyramid enforcement?▼

The limitation of automated test pyramid enforcement is that it strictly validates against a fixed 80% Unit, 15% API, and 5% E2E distribution. Projects requiring a different test ratio or specialized testing contexts may not fit this rigid configuration.

Related Skills

Explore More Software Engineering Skills→
yalehyaleh
21

Testing Strategy

Transform ad-hoc Go testing into a pattern-driven strategy with coverage analysis.

Community
Advanced
Thiago-Cruz-engThiago-Cruz-eng

testing-strategies

Design test pyramid strategies covering unit, integration, and E2E tests.

Community
Intermediate
FelipePepeFelipePepe

rule-testing

Define testing strategy, coverage targets, and quality gates for Vitest, Playwright, and Husky.

Community
Intermediate
ai-enhanced-engineerai-enhanced-engineer
3

unit-test-standards

Enforce Python unit test naming conventions and 80% coverage thresholds.

Official
Intermediate