Testing Strategist

Design testing strategies with framework setup, test levels, TDD, and CI/CD integration.

34|7|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/daffy0208/ai-dev-standards --skill testing-strategist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Testing Strategist
Source: https://github.com/daffy0208/ai-dev-standards/tree/main/SKILLS/testing-strategist
Command: npx skills add https://github.com/daffy0208/ai-dev-standards --skill testing-strategist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates uncertainty in software quality by providing a structured approach to testing that ensures comprehensive coverage while maintaining test performance.

Core Features & Use Cases

  • Testing Pyramid Implementation: Guides you through implementing the optimal 70% unit, 20% integration, 10% E2E test ratio.
  • Framework Selection: Helps choose and configure appropriate testing frameworks like Jest, React Testing Library, and Playwright.
  • Use Case: When starting a new React project, use this Skill to set up Jest for unit tests, configure API integration tests, and establish E2E testing for critical user flows.

Quick Start

Use the testing strategist skill to set up Jest testing for my React components and configure 70% code coverage targets.

Frequently Asked Questions about Testing Strategist

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

FAQPage Schema
How do I implement the testing pyramid strategy with the right ratio of unit, integration, and E2E tests?

The testing pyramid strategy recommends distributing tests as 70% unit tests, 20% integration tests, and 10% E2E tests. This ratio balances comprehensive coverage with test performance, ensuring fast feedback loops while validating critical user flows and system interactions.

How do I set up Jest and configure code coverage targets for a React project?

Jest is a popular testing framework for React projects. Configure Jest with coverage thresholds in your project settings, then write unit tests for components and utilities. Set target coverage at 70% to align with testing pyramid principles while maintaining practical, maintainable test suites.

What's the best way to choose between Jest, React Testing Library, and Playwright for different test levels?

Jest excels at unit and snapshot testing; React Testing Library focuses on component integration tests from a user perspective; Playwright handles E2E testing across browsers. Match each tool to its test level—Jest for 70% unit tests, React Testing Library for 20% integration, Playwright for 10% E2E.

Can I integrate my testing strategy with CI/CD pipelines?

Yes. Testing strategies designed around fast, isolated, repeatable, self-checking tests integrate seamlessly with CI/CD pipelines. Run unit tests first for rapid feedback, then integration and E2E tests in later stages to catch regressions before deployment.

How do I decide what to test at each level—unit, integration, and E2E?

Unit tests cover individual functions and components in isolation; integration tests validate interactions between components and APIs; E2E tests verify critical user workflows end-to-end. The 70/20/10 distribution ensures broad coverage while keeping slower E2E tests minimal.

Does test-driven development work with the testing pyramid approach?

Test-driven development (TDD) aligns naturally with the testing pyramid. Write unit tests first to guide implementation, add integration tests for component interactions, then E2E tests for user flows. This progression builds confidence while maintaining the 70/20/10 ratio.