test-strategy

Design a testing strategy with test pyramid, fixture isolation, and scenario matrix.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill test-strategy-vtrka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-strategy
Source: https://github.com/vTRKA/supervibe/tree/main/skills/test-strategy
Command: npx skills add https://github.com/vTRKA/supervibe --skill test-strategy-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents brittle or misleading test suites by turning feature requirements into a behavior-proof testing plan before you write tests.

Core Features & Use Cases

  • Test pyramid sizing: Sets unit/integration/e2e ratios by count and caps e2e by runtime.
  • Fixture isolation policy: Selects an explicit isolation mode and bans shared mutable state across tests.
  • Canonical scenario matrix: Produces a complete scenario set (happy, negative, boundary/null, degraded, concurrency/idempotency, time/locale/encoding, regression) with explicit statuses.
  • Browser/visual/effect proof overlay: Adds runtime evidence lanes, visual diff gates, motion/media fallbacks, performance budgets, and safety checks when advanced surfaces are involved.
  • Goal-to-scenario mapping: Ensures every required Goal ID is mapped to the needed scenario rows or has explicit N/A rationales, otherwise forces replan.

Quick Start

Ask your AI to produce a test strategy for the new feature and include the required scenario matrix, fixture isolation policy, flake budget, and browser/visual/effect proof lanes if relevant.

Frequently Asked Questions about test-strategy

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

FAQPage Schema
How do I design a test strategy that prevents flaky tests and high e2e runtime?▼

Design a test strategy by setting unit/integration/e2e ratios by count and capping e2e by runtime to prevent flaky tests. Enforce a fixture isolation policy that bans shared mutable state to keep suites reliable and deterministic.

What is a canonical scenario matrix and how does it map to feature requirements?▼

A canonical scenario matrix is a complete test set covering happy, negative, boundary, degraded, and concurrency paths. It maps required Goal IDs to explicit scenario statuses, forcing a replan if any goal lacks coverage or a valid N/A rationale.

How do I add browser proof and visual diff gates to my testing plan?▼

Add browser proof by applying a proof overlay with runtime evidence lanes, visual diff gates, motion fallbacks, performance budgets, and safety checks. This validates advanced visual and effect surfaces before final CI gates execute.

Why does my test coverage report look good but still miss real behavior?▼

Coverage reports miss real behavior when tests lack a scenario matrix targeting boundary, degraded, and concurrency paths. Mapping required Goal IDs to explicit scenario rows ensures coverage triangulation captures actual behavior, not just code execution.

When should I set a flake-rate SLO breach and replan my test pyramid?▼

Trigger a test strategy replan when flake-rate SLO breaches occur or when introducing new test layers. Redesign the test pyramid by resetting unit/integration/e2e ratios, enforcing fixture isolation, and re-mapping Goal IDs to the canonical scenario matrix.