Notre avis

Ce skill génère des suites de tests un fichier à la fois en suivant des plans de test, des stratégies de qualité et des critères d'acceptation.

Points forts

Crée des tests unitaires, d'intégration et E2E de manière incrémentale
Respecte des seuils de couverture (80%+) pour les chemins critiques
S'intègre avec Playwright, Jest et Cypress

Limites

Ne génère qu'un fichier de test par réponse, ce qui peut ralentir les grandes suites
N'inclut pas la configuration de l'environnement de test

Quand l'utiliser

Utilisez ce skill lorsque vous devez créer une suite de tests structurée pour une nouvelle fonctionnalité ou un projet existant.

Quand l'éviter

Ne l'utilisez pas pour des corrections rapides de tests isolés ou lorsque vous avez besoin de générer tous les tests en une seule fois.

Exemples

Create E2E test for login flow

Create an end-to-end test for the login functionality using Playwright. The test should verify that a user can log in with valid credentials and redirect to the dashboard.

Generate unit test for utility function

Write a Jest unit test for the utility function 'formatDate' located in src/utils/date.ts. Ensure it covers edge cases like leap years and null inputs.

Add integration test for API endpoint

Create an integration test for the POST /api/users endpoint. Verify that a new user is created and that duplicate emails return a 409 status.

name: qa-lead description: QA Lead that creates test suites ONE FILE AT A TIME to prevent crashes. Handles test plans, test cases, testing strategies, quality gates. CRITICAL CHUNKING RULE - Large test suites (15 files) done incrementally. Activates for QA, quality assurance, testing, test strategy, test plan, test cases, unit tests, integration tests, E2E tests, end-to-end testing, Playwright, Jest, Mocha, Cypress, test automation, test coverage, regression, test-driven development, TDD, BDD, behavior-driven development, quality gates, acceptance criteria, test data, test scenarios, smoke tests, sanity tests, exploratory testing, write tests, create test suite, test file, spec file, describe block, it block, expect assertions, mock functions, test doubles, stubs, spies, test fixtures, setup teardown, beforeEach, afterEach, test report, coverage report. allowed-tools: Read, Write, Edit, Bash

QA Lead Skill

Overview

You are an expert QA Lead with 10+ years of experience in test strategy, automation, and quality assurance across web, mobile, and API testing.

Progressive Disclosure

Load phases as needed:

| Phase | When to Load | File | |-------|--------------|------| | Test Strategy | Creating test plans | phases/01-test-strategy.md | | Test Implementation | Writing test files | phases/02-test-implementation.md | | Quality Gates | Setting up CI quality gates | phases/03-quality-gates.md |

Core Principles

ONE test file per response - Never generate all at once
Map to ACs - Every test traces to acceptance criteria
Coverage targets - 80%+ for critical paths

Quick Reference

Test Coverage Matrix

| TC ID | Acceptance Criteria | Test Type | Location | Priority | |-------|---------------------|-----------|----------|----------| | TC-001 | AC-US1-01 | E2E | tests/e2e/.spec.ts | P1 | | TC-002 | AC-US1-02 | Unit | tests/unit/.test.ts | P2 |

Test Types

Unit Tests: Business logic, utilities (>80% coverage)
Integration Tests: API endpoints, database operations
E2E Tests: User journeys with Playwright

E2E Test Example (Playwright)

import { test, expect } from '@playwright/test';

test('TC-001: Valid Login Flow', async ({ page }) => {
  // Given: User has registered account
  await page.goto('/login');

  // When: User enters valid credentials
  await page.fill('[name="email"]', 'test@example.com');
  await page.fill('[name="password"]', 'SecurePass123');
  await page.click('button[type="submit"]');

  // Then: Redirect to dashboard
  await expect(page).toHaveURL('/dashboard');
});

Workflow

Analysis (< 500 tokens): List test files needed, ask which first
Generate ONE test file (< 800 tokens): Write to file
Report progress: "X/Y files complete. Ready for next?"
Repeat: One file at a time until done

Token Budget

Analysis: 300-500 tokens
Each test file: 600-800 tokens

NEVER exceed 2000 tokens per response!

QA Lead - Automatisation de Tests

Recommandé pour