test-design

Guide test design with test pyramid principles and test doubles.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/nakano1122/dotfiles --skill test-design-nakano1122
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-design
Source: https://github.com/nakano1122/dotfiles/tree/main/dot_agents/skills/test-design
Command: npx skills add https://github.com/nakano1122/dotfiles --skill test-design-nakano1122

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to designing effective testing strategies, ensuring software quality and reliability without being tied to specific tools.

Core Features & Use Cases

  • Test Pyramid Guidance: Understand the optimal balance of unit, integration, and E2E tests.
  • Test Level Selection: Criteria for choosing the right test level for different scenarios.
  • Test Double Strategies: Guidance on using Stubs, Mocks, Fakes, and Spies effectively.
  • Use Case: When starting a new feature, use this Skill to determine the best testing approach, define what needs to be tested, and select appropriate testing techniques to ensure thorough coverage and maintainability.

Quick Start

Use the test-design skill to understand the principles of the test pyramid.

Frequently Asked Questions about test-design

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

FAQPage Schema
How do I design an effective test strategy for new software features?

Design a test strategy for new features by applying test pyramid principles to balance unit, integration, and E2E tests. Use selection criteria to choose the right test levels and prioritize test cases for thorough coverage and maintainability.

What is the difference between Stubs, Mocks, Fakes, and Spies in test design?

Stubs, Mocks, Fakes, and Spies are test doubles used to isolate software components during testing. Effective test double strategies involve selecting the correct double to replace dependencies, ensuring accurate verification without coupling to specific testing frameworks.

How do I select the right test level for different software testing scenarios?

Select the right test level by applying specific criteria to your testing scenarios, balancing the test pyramid. Determine whether unit, integration, or E2E tests are optimal based on the features being tested to ensure thorough coverage and maintainability.

What are common test design anti-patterns and how do I avoid them?

Common test design anti-patterns hinder software quality and maintainability. Avoid them by following universal test design patterns, adopting clear naming conventions, and carefully considering test coverage when working on bug fixes or legacy code.

Can I apply these test design principles without being tied to a specific testing framework?

Yes, you can apply these test design principles independently of specific testing frameworks. The guidance provides a universal strategy covering test pyramid principles, test double selection, and naming conventions applicable across any software stack.