testing-strategies

Zate's avatarfrom Zate

This skill should be used for test coverage, test pyramid, unit/integration/E2E test design, TDD, BDD, mocking strategies, test doubles, test architecture

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026
[Testing and QA]

When & Why to Use This Skill

This Claude skill provides expert guidance on comprehensive software testing strategies, including the test pyramid, TDD, BDD, and multi-level test design (Unit, Integration, and E2E). It helps developers establish robust test architectures, optimize code coverage guidelines, and implement effective mocking strategies to ensure high-quality, deployment-ready software.

Use Cases

  • Designing a balanced test suite using the test pyramid to optimize execution speed and resource allocation.
  • Implementing Test-Driven Development (TDD) or Behavior-Driven Development (BDD) workflows to improve code reliability and requirement alignment.
  • Defining mocking strategies and test doubles to isolate external dependencies and improve unit test performance.
  • Establishing integration and E2E testing patterns to validate critical user journeys and API contracts.
  • Developing a comprehensive test coverage strategy to ensure business logic and edge cases are thoroughly validated.
nametesting-strategies
descriptionThis skill should be used for test coverage, test pyramid, unit/integration/E2E test design, TDD, BDD, mocking strategies, test doubles, test architecture
whenToUseDesigning tests, coverage strategy, test pyramid, TDD, BDD, mocking, test doubles, test organization, E2E testing, integration testing strategy
whenNotToUseSimple test additions, established patterns, single test file edits
- skillsuperpowers:test-driven-development
whenwriting tests first, rigorous TDD discipline

Testing Strategies

Comprehensive test design for deployment readiness.

Test Pyramid

    /  E2E  \       Few, slow, expensive
   /  Integ  \      Some, medium
  /   Unit    \     Many, fast, cheap

Coverage Guidelines

Level Coverage Focus
Unit 80%+ Business logic
Integration Key paths APIs, DB
E2E Critical flows User journeys

Unit Test Patterns

  • Test one thing per test
  • Clear arrange/act/assert
  • Mock external dependencies
  • Fast execution (<1s each)

Integration Test Patterns

  • Test real dependencies
  • Use test databases
  • Clean up after tests
  • Cover API contracts

E2E Test Patterns

  • Critical user journeys only
  • Stable selectors
  • Retry flaky network calls
  • Parallel where possible