What is the recommended test distribution?

It follows a classic testing pyramid: 70% Unit tests for business logic, 20% Integration tests for components, and 10% E2E tests for user journeys.

How does it help with external dependencies?

It provides a comprehensive mocking strategy, recommending the use of test doubles, spies, and fakes to isolate units and simulate API responses.

Which programming languages are supported?

While the strategy concepts are universal, it provides specific framework guidance for JavaScript, TypeScript, and Python projects.

When should I use the Testing Strategy skill?

This skill is designed to be used after you have completed code development but before submitting your work for a formal code review.

Does this skill modify my source code directly?

No, the Testing Strategy skill is configured to use read-only commands (Read, Grep, Glob) to analyze your files without making any modifications.

Testing Strategy Specialist

Name: Testing Strategy Specialist
Author: nicholasgriffintn

bynicholasgriffintn

Security & Testing

Designs and implements comprehensive testing strategies to ensure codebase quality and reliability before the code review process.

About

The Testing Strategy skill provides a structured, expert-led approach to quality assurance within the Claude Code environment. By analyzing your codebase using a read-only workflow, it helps developers establish a balanced testing pyramid that prioritizes fast unit tests while maintaining critical integration and end-to-end coverage. The skill provides specific framework recommendations for JavaScript, TypeScript, and Python environments, defines rigorous coverage thresholds, and outlines sophisticated mocking patterns to isolate dependencies, ensuring your software remains maintainable and bug-free throughout its lifecycle.

Key Features

Strategic mocking guidelines for external APIs and services
Tailored framework selection for Vitest, Playwright, and Pytest
Identification of critical edge cases and error handling scenarios
Automated testing pyramid design with 70/20/10 ratio distribution
Definition of minimum coverage thresholds for unit and integration tests
0 GitHub stars

Use Cases

Auditing existing test suites to identify coverage gaps in business logic
Establishing a testing foundation for new feature development
Designing integration tests for complex API and service interactions

About

Key Features

Strategic mocking guidelines for external APIs and services
Tailored framework selection for Vitest, Playwright, and Pytest
Identification of critical edge cases and error handling scenarios
Automated testing pyramid design with 70/20/10 ratio distribution
Definition of minimum coverage thresholds for unit and integration tests
0 GitHub stars

Use Cases

Auditing existing test suites to identify coverage gaps in business logic
Establishing a testing foundation for new feature development
Designing integration tests for complex API and service interactions