testing-strategy

Test planning and coverage strategy workflow. Use when designing test suites, establishing coverage targets, planning TDD approaches, or assessing testing gaps in existing codebases.

Ir para a instalação

Repositório: ar4mirez/samuel
Última atividade na origem: 12 de fevereiro de 2026 às 15:54
Idioma detectado do SKILL.md: inglês
Estrelas: 7
Forks: 1

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/ar4mirez/samuel --skill testing-strategy

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

sync-claude-md

Sync per-folder CLAUDE.md and AGENTS.md files with context-aware content. Use after structural changes, adding new directories, refactoring, or periodic maintenance to keep folder-level AI instructions current.

2026-02-20

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

2026-02-20

auto

Autonomous AI coding loop (Ralph Wiggum methodology). Use when running AI agents in unattended/autonomous mode to independently select and complete tasks from a structured task list (prd.json). Enables AFK development across multiple context windows.

2026-02-20

Ver todas deste repositório

Phase 1: Coverage Analysis
    ↓
Phase 2: Critical Path Identification
    ↓
Phase 3: Test Pyramid Planning
    ↓
Phase 4: Test Prioritization
    ↓
Phase 5: Edge Case Planning
    ↓
Phase 6: Flaky Test Remediation
    ↓
Phase 7: Implementation Roadmap

npm test -- --coverage
# or
npx vitest run --coverage

pytest --cov=src --cov-report=html

go test -cover ./...
go test -coverprofile=coverage.out ./...
go tool cover -html=coverage.out

cargo tarpaulin --out Html

Lowest Coverage Files:
1. src/auth/oauth.ts - 12% (critical!)
2. src/api/payments.ts - 28% (critical!)
3. src/services/email.ts - 35%
4. src/utils/validation.ts - 42%
5. src/api/users.ts - 48%

Path	Description	Files	Priority
Authentication	Login, logout, session	auth/*	P0
Checkout	Cart → Payment → Confirm	payments/, cart/	P0
Registration	Signup → Verify → Profile	users/, email/	P1
Search	Query → Results → Filter	search/, api/	P1

src/auth/login.ts        - 45% coverage
src/auth/session.ts      - 52% coverage
src/auth/middleware.ts   - 88% coverage
src/models/user.ts       - 72% coverage

Authentication Path:
- Total lines: 450
- Covered lines: 267
- Coverage: 59% (target: 90%)
- Gap: 183 lines to cover

         /\
        /  \
       / E2E \         10% - Slow, expensive, covers user flows
      /______\
     /        \
    /Integration\      20% - Medium speed, covers integrations
   /______________\
  /                \
 /    Unit Tests    \  70% - Fast, cheap, covers logic
/____________________\

Current State:
- Unit tests: 45 (60%)
- Integration: 25 (33%)
- E2E: 5 (7%)

Ideal State:
- Unit tests: 70 (70%)
- Integration: 20 (20%)
- E2E: 10 (10%)

Gap:
- Need +25 unit tests
- Need -5 integration tests (or OK)
- Need +5 E2E tests

Priority	Criteria	Example
P0	Critical path, no tests	Payment processing
P1	Critical path, low coverage	Authentication
P2	High risk, medium coverage	Data validation
P3	Medium risk, any coverage	Utility functions
P4	Low risk, nice to have	Formatting helpers

## Test Backlog

### P0 - Immediate (This Sprint)
- [ ] Unit: payment.processPayment()
- [ ] Unit: auth.validateToken()
- [ ] Integration: POST /api/payments
- [ ] E2E: Complete checkout flow

### P1 - High (Next Sprint)
- [ ] Unit: auth.refreshToken()
- [ ] Unit: user.validateEmail()
- [ ] Integration: GET /api/users/:id
- [ ] E2E: Registration flow

### P2 - Medium (Backlog)
- [ ] Unit: validation helpers
- [ ] Unit: formatting utilities
- [ ] Integration: Search API

### P3 - Low (Nice to Have)
- [ ] Unit: logging utilities
- [ ] Unit: config loaders

Category	Cases	Example
Null/Undefined	null, undefined input	`validateUser(null)`
Empty	"", [], {}	`searchUsers("")`
Boundary	0, -1, MAX_INT	`setQuantity(0)`
Invalid Type	Wrong type input	`calculatePrice("abc")`
Concurrent	Race conditions	Parallel updates

Cause	Symptom	Fix
Timing	Random timeouts	Use proper async/await
Order dependency	Fails when run alone	Reset state in beforeEach
Shared state	Random failures	Isolate test data
External services	Network failures	Mock external calls
Date/time	Fails at midnight	Mock dates

## Sprint 1: Critical Path (2 weeks)

### Goals
- Achieve 90% coverage on authentication
- Achieve 90% coverage on payments
- Add 5 E2E tests for critical paths

### Tasks
1. Unit tests for auth module (20 tests)
2. Unit tests for payment module (15 tests)
3. Integration tests for auth API (5 tests)
4. E2E test: Complete checkout (1 test)
5. E2E test: Login flow (1 test)

### Expected Outcome
- Overall coverage: 55% → 65%
- Critical path coverage: 59% → 90%

describe('Module or Function', () => {
  // Setup
  beforeEach(() => {
    // Reset state
  });

  describe('method or scenario', () => {
    it('should [expected behavior] when [condition]', () => {
      // Arrange
      const input = createTestInput();

      // Act
      const result = functionUnderTest(input);

      // Assert
      expect(result).toEqual(expectedOutput);
    });
  });
});

should [expected behavior] when [condition]

Examples:
- should return user when valid ID provided
- should throw error when user not found
- should update timestamp when saving

# Node.js
npm test -- --coverage --coverageReporters=text-summary

# Python
pytest --cov=src --cov-report=term-missing

# Go
go test -cover ./... | grep -E "coverage:"

# Rust
cargo tarpaulin --out Stdout

describe('functionName', () => {
  it('should [behavior] when [condition]', () => {
    const result = functionName(input);
    expect(result).toEqual(expected);
  });
});

describe('POST /api/resource', () => {
  it('should create resource when valid data', async () => {
    const response = await request(app)
      .post('/api/resource')
      .send(validData);
    expect(response.status).toBe(201);
  });
});

name	testing-strategy
description	Test planning and coverage strategy workflow. Use when designing test suites, establishing coverage targets, planning TDD approaches, or assessing testing gaps in existing codebases.
license	MIT
metadata	{"author":"samuel","version":"1.0","category":"workflow"}

Trigger	Description
Post-COMPLEX Feature	After implementing major features
Coverage Drop	When coverage falls below thresholds
Test Debt Sprint	Dedicated testing improvement effort
New Project	Establishing testing foundation
Pre-Release	Ensuring quality before deployment

Category	Target	Warning	Critical
Business Logic	>80%	70-80%	<70%
Overall

name	testing-strategy
description	Test planning and coverage strategy workflow. Use when designing test suites, establishing coverage targets, planning TDD approaches, or assessing testing gaps in existing codebases.
license	MIT
metadata	{"author":"samuel","version":"1.0","category":"workflow"}

Trigger	Description
Post-COMPLEX Feature	After implementing major features
Coverage Drop	When coverage falls below thresholds
Test Debt Sprint	Dedicated testing improvement effort
New Project	Establishing testing foundation
Pre-Release	Ensuring quality before deployment

Area	Target	Current	Gap
`src/auth/`	90%	45%	-45%
`src/api/`	80%	62%	-18%
`src/utils/`	60%	78%	+18%
Overall	60%	55%	-5%

Test Type	Effort	Coverage Impact
Unit (simple)	15 min	High
Unit (complex)	1 hour	High
Integration	2 hours	Medium
E2E	4 hours	Low (but valuable)

Week	Overall	Business	Critical	Tests Added
1	55%	62%	59%	+15
2	62%	75%	78%	+22
3	68%	82%	88%	+18
4	72%	85%	92%	+12

testing-strategy

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Testing Strategy

When to Use

Coverage Targets

Testing Strategy

When to Use

Coverage Targets

Prerequisites

Strategy Process

Phase 1: Coverage Analysis

1.1 Generate Coverage Report

1.2 Analyze Coverage Gaps

1.3 Identify Uncovered Files

Phase 2: Critical Path Identification

2.1 Define Critical Paths

2.2 Map Critical Files

2.3 Calculate Critical Path Coverage

Phase 3: Test Pyramid Planning

3.1 Ideal Test Pyramid

3.2 Current Distribution

3.3 Test Type Guidelines

Phase 4: Test Prioritization

4.1 Priority Matrix

4.2 Effort Estimation

4.3 Prioritized Test Backlog

Phase 5: Edge Case Planning

5.1 Required Edge Cases

5.2 Edge Case Checklist

Phase 6: Flaky Test Remediation

6.1 Identify Flaky Tests

6.2 Common Causes & Fixes

Phase 7: Implementation Roadmap

7.1 Sprint Planning Template

7.2 Test Writing Guidelines

7.3 Coverage Tracking

Quick Reference

Coverage Commands

Test Templates

Checklist

Analysis

Planning

Implementation

Validation

Extended Resources

Related Resources