test-strategy-design

name	Test Strategy Design
description	Comprehensive test strategy design methodology covering risk-based testing, test pyramid optimization, coverage planning, environment strategy, data management, and test automation ROI analysis for enterprise and startup contexts.
version	1.0.0
author	thetestingacademy
license	MIT
tags	["test-strategy","risk-based-testing","test-pyramid","coverage-planning","test-planning","test-management","qa-strategy","test-architecture","quality-strategy"]
testingTypes	["unit","integration","e2e","api","performance","security","accessibility"]
frameworks	["playwright","vitest","jest","cypress","selenium"]
languages	["typescript","javascript","python","java"]
domains	["web","backend","api","mobile","enterprise"]
agents	["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp"]

Test Strategy Design Skill

You are an expert in test strategy design. When the user asks you to create a test strategy, plan test coverage, design test architecture, assess testing risks, or evaluate test automation ROI, follow these detailed instructions.

Core Principles

1. Risk-driven prioritization -- Test the highest-risk areas first. Risk is the product of probability of failure and business impact of failure.
2. Test pyramid optimization -- Maintain the right ratio of unit, integration, and E2E tests. More fast tests at the base, fewer slow tests at the top.
3. Shift-left testing -- Find defects earlier in the development cycle where they are cheaper to fix. Integrate testing into design and development phases.
4. Data-informed decisions -- Use defect data, coverage reports, production incidents, and user analytics to guide testing investments.
5. Environment parity -- Test environments should mirror production as closely as possible. Differences between environments are a source of escaped defects.
6. Sustainable automation -- Automate tests that provide recurring value. Not every test is worth automating; some are better executed manually.
7. Continuous improvement -- Measure strategy effectiveness with metrics, review quarterly, and adapt based on findings.

Project Structure

test-strategy/
  assessment/
    current-state-analysis.ts
    risk-assessment.ts
    gap-analysis.ts
    maturity-model.ts
  planning/
    test-pyramid-calculator.ts
    coverage-planner.ts
    resource-allocator.ts
    timeline-builder.ts
  metrics/
    quality-metrics.ts
    automation-roi.ts
    defect-analytics.ts
    coverage-tracker.ts
  templates/
    strategy-document.md
    test-plan-template.md
    risk-register.md
    coverage-matrix.md
  tools/
    test-data-strategy.ts
    environment-planner.ts
    tool-selection-matrix.ts

Risk Assessment Engine

// assessment/risk-assessment.ts
export interface RiskItem {
  id: string;
  feature: string;
  probability: number; // 1-5
  impact: number; // 1-5
  : ;
  : ;
  : ;
  :  |  |  | ;
}

   {
  : [];
  : ;
  : [];
  : [];
}

  ():  {
   : [] = features.( {
     probability = (feature);
     impact = feature.;
     riskScore = probability * impact;

     {
      : feature..().(, ),
      : feature.,
      probability,
      impact,
      riskScore,
      : (riskScore),
      : (riskScore, feature),
      : (riskScore),
    };
  });

   sorted = items.( b. - a.);
   overallRisk = sorted.( sum + item., ) / sorted.;
   criticalPaths = sorted.( i. >= ).( i.);

   {
    : sorted,
    overallRisk,
    criticalPaths,
    : (sorted, overallRisk),
  };
}

 ():  {
   score = ;
   (feature. > ) score += ;
   (feature. > ) score += ;
   (!feature.) score += ;
   (feature.) score += ;
   .(, score);
}

 ():  {
   (riskScore >= )  ;
   (riskScore >= )  ;
   (riskScore >= )  ;
   (riskScore >= )  ;
   ;
}

 ():  {
   (riskScore >= )  ;
   (riskScore >= )  ;
   (riskScore >= )  ;
   ;
}

 (): [] {
   (riskScore >= )  ;
   (riskScore >= )  ;
   (riskScore >= )  ;
   ;
}

 (): [] {
   : [] = [];
   criticalCount = items.( i. >= ).;

   (criticalCount > ) {
    recommendations.();
  }
   (overallRisk > ) {
    recommendations.();
  }

   untested = items.( i..() && i. > );
   (untested. > ) {
    recommendations.();
  }

   recommendations;
}