test-strategy

Generate test strategy documents from source code directories using pyramid ratios and mutation testing.

75|13|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/avelikiy/great_cto --skill test-strategy-avelikiy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-strategy
Source: https://github.com/avelikiy/great_cto/tree/main/skills/test-strategy
Command: npx skills add https://github.com/avelikiy/great_cto --skill test-strategy-avelikiy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill solves the challenge of turning abstract coverage percentages into actionable and defensible test plans. It provides a systematic approach to test case design based on archetype-specific pyramid ratios, case selection methods, and mutation testing for code coverage validation.

Core Features & Use Cases

  • Test Coverage Analysis: Provides guidelines for setting up and interpreting test coverage using pyramid ratios.
  • Case Selection: Offers a framework for selecting equivalence classes, boundaries, and property-based tests to ensure thorough coverage.
  • Mutation Score: Incorporates mutation testing to ensure that the tests are not just running the code but also detecting errors.
  • ** Flake Quarantine**: Helps manage flaky tests, ensuring that they do not rot the test signal over time.

Quick Start

Run the skill and provide the path to your source code directory. The skill will generate a test strategy document with pyramid ratios, case selection details, mutation score results, and flake quarantine policies.

Frequently Asked Questions about test-strategy

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

FAQPage Schema
How do I turn code coverage percentages into a defensible test strategy?

Turn code coverage percentages into a defensible test strategy by applying archetype-based pyramid ratios, equivalence class selection, and mutation testing to validate that tests detect errors rather than simply executing code.

What is the best way to plan test cases for a large feature development scenario?

Plan test cases for large feature scenarios by analyzing source code directories to generate archetype-specific pyramid ratios, select equivalence classes and boundaries, and define property-based tests for thorough coverage.

How do I generate a test plan from an existing source code directory?

Generate a test plan from a source code directory by running the analysis against your code and documentation to output a strategy document containing pyramid ratios, case selection details, mutation score results, and flake quarantine policies.

Why does high test coverage not guarantee my tests are catching errors?

High test coverage does not guarantee error detection because tests may execute code without asserting correct behavior. Mutation testing validates test quality by injecting code changes to verify your test suite detects the defects.

How do I manage flaky tests to prevent them from degrading the test signal?

Manage flaky tests to prevent signal degradation by applying flake quarantine policies that isolate inconsistent test failures, ensuring transient issues do not rot the reliability of your overall test suite over time.

Does this test planning approach require specific testing frameworks to work?

This test planning approach does not require specific testing frameworks. It requires analyzing your source code and documentation to generate a systematic test strategy using pyramid ratios, equivalence classes, and mutation testing.