testing

Plan testing strategies for unit, integration, and end-to-end layers.

3|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/deandum/claude-resources --skill testing-deandum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/deandum/claude-resources/tree/main/skills/core/testing
Command: npx skills add https://github.com/deandum/claude-resources --skill testing-deandum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan and enforce a robust testing strategy across codebases, ensuring tests are correctly scoped, maintainable, and aligned with quality goals.

Core Features & Use Cases

  • Unit-test-centric guidance: define the right balance of unit, integration, and end-to-end tests.
  • Mocking and boundary decisions: decide where to isolate components and how to simulate dependencies.
  • Regression discipline: mandate regression tests for bug fixes and clarity on test coverage.

Quick Start

Plan and document a test strategy for the new feature, including unit vs integration decisions and regression planning.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I define a balanced test strategy for unit, integration, and end-to-end tests?

A balanced test strategy applies the test pyramid by defining criteria for unit coverage, integration boundaries, and regression tests. Plan the right mix of unit, integration, and end-to-end tests to ensure maintainable and correctly scoped quality checks across your codebase.

What is the best way to mandate regression tests for bug fixes?

Regression discipline for bug fixes mandates adding specific regression tests to prevent recurrence. Plan and document a test strategy that includes clear testing artifacts and coverage criteria to enforce this discipline across feature development and system-wide QA.

How do I decide where to mock dependencies and set integration boundaries?

Setting integration boundaries requires deciding where to isolate components and how to simulate dependencies. Define mocking strategies within your test plan to correctly scope integration tests and ensure components are properly isolated during feature development.

When do I need a formal test plan for feature development cycles?

A formal test plan is needed when planning feature development cycles, bug fixes, or system-wide QA. It helps govern your testing strategy by outlining unit versus integration decisions and regression planning to align tests with quality goals.

Can I use this testing strategy for system-wide QA across multiple layers?

Yes, this testing strategy applies to system-wide QA across unit, integration, and end-to-end layers. It helps teams plan and enforce robust testing across codebases by defining clear testing artifacts, mocking boundaries, and regression discipline.

Why does my unit test coverage fail to catch integration layer bugs?

Unit test coverage fails to catch integration bugs when boundaries for integration tests are poorly defined. Establish clear integration boundaries and mocking decisions to ensure tests are correctly scoped and maintainable across the test pyramid.