Designing Tests

This is your testing strategy companion for when you need to add tests to a codebase or debug why they're failing. It gives you the full testing pyramid breakdown (70% unit, 20% integration, 10% E2E), framework recommendations across JavaScript, Python, and Go, and concrete templates for each test type following the arrange-act-assert pattern. The coverage thresholds are sensible (80% global, 95% for core modules), and the mock-versus-real guidance actually helps you avoid common pitfalls like mocking internal modules. Load it when you're setting up testing infrastructure from scratch or trying to hit coverage targets without writing garbage tests.

skills.sh installs: 180
GitHub stars: 1.4K
last updated: Jun 9, 2026

View on GitHub

Install

$ npx -y skills add cloudai-x/claude-workflow-v2 --skill designing-tests --agent claude-code

Installs into .claude/skills of the current project.

Files

Designing Tests

When to Load

Trigger: Adding tests, test strategy planning, improving coverage, setting up testing infrastructure
Skip: Non-test code changes where testing is not part of the task

Test Implementation Workflow

Copy this checklist and track progress:

Test Implementation Progress:
- [ ] Step 1: Identify what to test
- [ ] Step 2: Select appropriate test type
- [ ] Step 3: Write tests following templates
- [ ] Step 4: Run tests and verify passing
- [ ] Step 5: Check coverage meets targets
- [ ] Step 6: Fix any failing tests

Testing Pyramid

Apply the testing pyramid for balanced coverage:

        /\
       /  \     E2E Tests (10%)
      /----\    - Critical user journeys
     /      \   - Slow but comprehensive
    /--------\  Integration Tests (20%)
   /          \ - Component interactions
  /------------\ - API contracts
 /              \ Unit Tests (70%)
/________________\ - Fast, isolated
                   - Business logic focus