skills.rest
prapanch
prapanchCOMMUNITY
Explore all skills by this author →
GitHub

test-strategy

Create unit, integration, and end-to-end testing plans prioritizing business rules and edge cases.

Updated Aug 23, 2026
Search Tags:#code quality#unit tests#testing#integration tests#regression testing#e2e testing#test design
One-click install
npx skills add https://github.com/prapanch/agent-coda --skill test-strategy-prapanch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-strategy
Source: https://github.com/prapanch/agent-coda/tree/main/app/test-strategy
Command: npx skills add https://github.com/prapanch/agent-coda --skill test-strategy-prapanch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you choose what to test and how to test it so your AI-written or AI-reviewed code gains real shipping confidence without wasting time on low-value or flaky coverage.

Core Features & Use Cases

  • Testing pyramid guidance: Use a practical unit/integration/e2e mix to balance speed, reliability, and confidence.
  • Targeted test selection: Focus on business rules, edge cases, error paths, and regressions while avoiding tests for framework behavior, library internals, or trivial constant code.
  • Actionable test quality heuristics: Detect and fix common test smells like flakiness, slowness, brittleness, god tests, and assertion duplication.

Quick Start

Tell your AI to propose a unit/integration/e2e testing plan for a new feature and include the specific behaviors, edge cases, and error paths that must be covered first.

Frequently Asked Questions about test-strategy

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

FAQPage Schema
How do I build a testing plan that covers the right unit, integration, and e2e tests?▼

A testing plan balances unit, integration, and e2e tests to prioritize business rules, edge cases, and error paths. This approach ensures code changes are validated with confidence while avoiding low-value or flaky coverage.

What is the best way to choose which behaviors to target for unit tests and integration tests?▼

Target business rules, edge cases, error paths, and regressions when choosing unit and integration tests. Avoid testing framework behavior, library internals, or trivial constant code to maintain high-value, confident coverage.

How do I fix flaky tests and other common test smells in my codebase?▼

Fix flaky tests and common test smells by applying actionable quality heuristics that detect slowness, brittleness, god tests, and assertion duplication. This ensures your test suite remains reliable and maintainable.

Do I need end-to-end testing for every new feature, or is a unit and integration mix enough?▼

An end-to-end testing mix is not always needed for every feature. A practical unit, integration, and e2e mix balances speed, reliability, and confidence, prioritizing e2e tests only when broader workflow validation is required.

How do I write regression tests when fixing a bug in an AI-generated code workflow?▼

Write regression tests for bug fixes by following a specific regression protocol that validates the error path. This ensures AI-reviewed software changes are protected against recurring issues and maintains shipping confidence.

Related Skills

Explore More Software Engineering Skills→
jshsakurajshsakura
22

qa-expert

Define risk-based test scope and acceptance criteria for software releases.

Community
Advanced
haidonglethqbhaidonglethqb

ck:test

Automate unit, integration, e2e, and UI tests with coverage analysis.

Community
Advanced
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
ryan-nguyen-01ryan-nguyen-01
4

agent-tester

Generates unit, integration, and e2e tests from code diffs and orchestrator context.

Community
Advanced