testing-strategy

Design test strategies using Marick's quadrants and risk-based selection.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cjohnhanson/codelikecody --skill testing-strategy-cjohnhanson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-strategy
Source: https://github.com/cjohnhanson/codelikecody/tree/main/skills/testing-strategy
Command: npx skills add https://github.com/cjohnhanson/codelikecody --skill testing-strategy-cjohnhanson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design robust test strategies for software systems by applying proven frameworks that help teams choose appropriate test shapes, align test coverage with risk, and optimize regression selection across releases.

Core Features & Use Cases

  • Shape-driven test architecture guidance (pyramid, trophy, diamond) to map test types to system architecture.
  • Quadrant-based coverage planning following Marick's model to balance unit, integration, functional, and exploratory tests.
  • Risk-based test selection and RCRCRC regression prioritization to focus on high-impact areas and recent changes.
  • Coverage of specialized techniques (contract testing, property-based testing, mutation testing) to strengthen test quality.
  • Quick-start-oriented guidance for evaluating and designing test strategies for a feature or project.

Quick Start

Design a strategy by selecting an architectural shape, auditing quadrant coverage, and applying risk-based prioritization to plan your first release.

Frequently Asked Questions about testing-strategy

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

FAQPage Schema
How do I design a test strategy that fits my software architecture?

To design a test strategy, you select an architectural shape model like a pyramid, trophy, or diamond, then map your unit, integration, and end-to-end tests to match your specific system architecture.

What is Marick's quadrants model for test coverage planning?

Marick's quadrants model is a framework for balancing test coverage that helps you align unit, integration, functional, and exploratory tests across your project to ensure comprehensive risk mitigation.

How do I use risk-based testing to prioritize regression test selection?

Risk-based testing prioritizes regression selection by applying the RCRCRC framework to focus test execution on high-impact areas and recent changes, optimizing release cycles.

When should I use specialized testing techniques like contract and mutation testing?

Specialized testing techniques like contract testing, property-based testing, and mutation testing are used to strengthen test quality when standard test shapes are insufficient for complex architectures.

Does this test strategy guidance work for microservices and SPAs?

Yes, this test strategy guidance applies to monoliths, single-page applications, and microservices, enabling you to plan balanced unit, integration, and end-to-end tests across these architectures.

What is the best way to balance unit and end-to-end tests in a complex system?

The best way to balance tests is applying Beck's test desiderata and Google's test size classification alongside architectural shape models to categorize and optimize your test suite distribution.