{"enrichment":{"faq":[{"a":"Testing Strategist guides you through the testing pyramid: 70% unit tests, 20% integration tests, 10% E2E tests. This structure balances speed, cost, and confidence. Unit tests verify individual functions and components quickly. Integration tests validate how modules work together\u2014especially critical for API endpoints and database operations. E2E tests with Playwright confirm real user workflows. Testing Strategist helps you choose the right test type for each scenario and implement them across business logic, React components, hooks, and API routes.","q":"What is the testing pyramid and how should Testing Strategist help me apply it?"},{"a":"Testing Strategist teaches test-driven development by walking you through the red-green-refactor cycle. First, write a failing test (red) that describes the desired behavior. Then write minimal code to make it pass (green). Finally, refactor both test and implementation for clarity and maintainability (refactor). This approach ensures your code is testable from the start, reduces bugs, and creates living documentation. Testing Strategist provides TDD tutorials and examples for React components, async patterns, and business logic.","q":"How do I write tests before code using the TDD red-green-refactor cycle?"},{"a":"Testing Strategist emphasizes organizing tests by the pyramid: keep unit tests fast and isolated, use mocks for external dependencies, and group tests by feature or module. For integration tests, mock only external services while testing real interactions between your components. E2E tests should cover critical user journeys. Testing Strategist recommends clear file structure\u2014colocating tests near source files or in a dedicated test directory\u2014and setting Jest coverage thresholds to maintain quality as your project grows.","q":"What are the best practices for the testing pyramid and structuring tests?"},{"a":"Testing Strategist walks you through configuring each tool. Jest handles unit and integration tests with coverage reporting and configurable thresholds. React Testing Library focuses on testing components as users interact with them, avoiding implementation details. Playwright automates E2E testing across browsers. Testing Strategist provides setup guides for Next.js projects, shows how to configure Jest coverage thresholds, and explains when to use mocks for external APIs versus real test doubles.","q":"How do I set up Jest, React Testing Library, and Playwright for my project?"},{"a":"Testing Strategist helps identify gaps in coverage by analyzing which code paths lack tests and recommends which scenarios to prioritize. It guides you toward realistic coverage targets and explains how to test async code patterns, form interactions, and edge cases. For flaky tests, Testing Strategist teaches debugging techniques: isolate test dependencies, avoid timing assumptions, use proper async/await patterns, and ensure mocks are reset between tests. Structured testing practices eliminate most flakiness.","q":"How can Testing Strategist help me improve code coverage and fix flaky tests?"},{"a":"Testing Strategist clarifies each layer: unit tests verify single functions or components in isolation using mocks\u2014fast and focused. Integration tests validate how multiple modules interact, like testing React components with real hooks or API endpoints with databases. E2E tests with Playwright simulate real users navigating your app across browsers\u2014slow but highest confidence. Testing Strategist helps you choose the right balance: prioritize unit tests for speed, use integration tests for critical workflows, and E2E tests for user-facing features.","q":"What's the difference between unit, integration, and E2E tests in Testing Strategist?"}],"shadow_tags":["test-pyramid","quality-assurance","tdd-workflow","code-reliability","test-automation","coverage-metrics","qa-strategy","testing-frameworks","ci-cd-testing"],"summary_rewrite":"Testing Strategist helps you build a structured testing approach grounded in the testing pyramid\u201470% unit tests, 20% integration tests, 10% E2E tests. It covers practical implementation across business logic, React components, hooks, API routes, and database operations, plus test-driven development principles to ship with confidence."},"files":[{"bytes":22883,"path":"skills/testing-strategist/SKILL.md","sha256":"104b174797b13ea1a349bf5ee9a20bf441527585449f9c654b4a5c83d1967a0a","url":"https://skillfed.io/files/daffy0208/ai-dev-standards/testing-strategist/b3806094/SKILL.md"}],"id":"daffy0208/ai-dev-standards/testing-strategist","links":{"html":"https://skillfed.io/daffy0208/ai-dev-standards/testing-strategist","md":"https://skillfed.io/daffy0208/ai-dev-standards/testing-strategist.md","repo":"https://github.com/daffy0208/ai-dev-standards"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":7,"language":"TypeScript","last_updated":"2025-12-25","license":"MIT","name":"Testing Strategist","publisher":"daffy0208","stars":32},"relations":{"similar":[{"id":"jmsktm/claude-settings/testing-qa"},{"id":"alinaqi/maggy/react-web"},{"id":"organvm/a-i--skills/testing-patterns"},{"id":"pluginagentmarketplace/custom-plugin-react-native/react-native-testing"},{"id":"bobmatnyc/claude-mpm-skills/jest"},{"id":"majesticlabs-dev/majestic-marketplace/react-testing"},{"id":"manutej/luxor-claude-marketplace/jest-react-testing"},{"id":"affaan-m/ECC/react-testing"},{"id":"nahisaho/MUSUBI/test-engineer"},{"id":"joneqian/claude-skills-suite/tdd-workflow"}]},"slug":{"owner":"daffy0208","repo":"ai-dev-standards","skill":"testing-strategist"},"version":"b3806094"}