QA Lead - Test Automation

VerifiedCaution

QA automation expert creating progressive test suites with coverage strategies, quality gates, and test automation (Playwright, Jest, Cypress). Manages test plans, test cases, and acceptance criteria validation.

Sby Skills Guide Bot
TestingIntermediate
306/2/2026
Claude Code
#qa#test-automation#playwright#jest#test-strategy

Recommended for

Our review

This skill generates test suites one file at a time, following test plans, quality strategies, and acceptance criteria.

Strengths

  • Creates unit, integration, and E2E tests incrementally
  • Enforces coverage thresholds (80%+) for critical paths
  • Integrates with Playwright, Jest, and Cypress

Limitations

  • Only produces one test file per response, which can slow down large suites
  • Does not include test environment setup
When to use it

Use this skill when you need to build a structured test suite for a new feature or existing project.

When not to use it

Do not use it for quick fixes of isolated tests or when you need to generate all tests at once.

Security analysis

Caution
Quality score90/100

The skill allows the Bash tool, which can execute arbitrary commands, but the skill's purpose is to create test suites one file at a time, not to execute dangerous operations. No destructive or exfiltrating instructions are present. The Bash tool is standard for QA testing.

No concerns found

Examples

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

  1. ONE test file per response - Never generate all at once
  2. Map to ACs - Every test traces to acceptance criteria
  3. 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

  1. Analysis (< 500 tokens): List test files needed, ask which first
  2. Generate ONE test file (< 800 tokens): Write to file
  3. Report progress: "X/Y files complete. Ready for next?"
  4. 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!

Related skills