skills.rest
jacob-balslev
jacob-balslevCOMMUNITY
Explore all skills by this author →
GitHub

testing-strategy

Plan automated test coverage by selecting scope and test level.

1|Updated May 6, 2026
Search Tags:#testing#quality assurance#regression testing#test planning#evidence quality#failure cases#test level selection
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill testing-strategy-jacob-balslev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-strategy
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/testing-strategy
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill testing-strategy-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing-strategy helps you decide what to test, at what level, and with what evidence so changes get verified efficiently and regressions are actually caught.

Core Features & Use Cases

  • Test-scope decisions: decide which behaviors deserve maintenance-cost and which do not.
  • Test-level selection: choose between unit, integration, contract, and e2e based on risk and coupling.
  • Effort-to-risk matching: invest verification effort where failures are most likely and most damaging.
  • Regression targeting & evidence quality: pin the specific risky behavior with concrete, reproducible checks, including failure cases and boundaries.

Quick Start

Plan a verification approach by running the testing-strategy guidance for your change and writing a checklist that explicitly states the behavior target, the test level, and the evidence.

Frequently Asked Questions about testing-strategy

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

FAQPage Schema
How do I decide what automated tests to write for a bug fix or feature?▼

Test level selection depends on risk and coupling: use unit tests for isolated logic, integration tests for coupled modules, contract tests for service boundaries, and e2e tests for critical user journeys. Match the verification effort to the likelihood and impact of failures.

What's the best way to target regression testing without over-testing?▼

Test scope decisions should exclude debugging work, documentation updates, and integration-test-design tasks. Focus strictly on software verification: selecting what behaviors to test, which test level applies, and what concrete evidence confirms the change works without misclassifying non-verification work.

How do I create a test plan checklist for a code refactor?▼

Before test planning, define explicit behavior and regression targets for the bug fix, feature, or refactor. You need concrete verification evidence and identified failure cases to input into the test level selection process and produce a coverage checklist.

When should I skip adding automated tests for a new feature?▼

After test planning, execute the selected unit, integration, contract, or e2e tests and collect concrete verification evidence. Run the regression checks against failure cases and boundaries to validate the behavior targets and produce a reproducible test outcome report.

Related Skills

Explore More Software Engineering Skills→
JKhyroJKhyro

test-driven-development

Enforce test-first implementation with failing tests before production code.

Community
Advanced
Obsidian-OwlObsidian-Owl
4

speckit-test-review

Assess test quality across unit, integration, contract, and e2e tests.

Official
Advanced
jpoutrinjpoutrin
14

qa-testing-methodology

Design test cases for happy path, validation, edge, error, and permission scenarios.

Community
Basic
mbwsimsmbwsims
71

hotspots

Identify high-risk files in a codebase using churn, complexity, and coupling.

Community
Intermediate