← ClaudeAtlas

test-engineeringlisted

Use when designing test strategies, planning coverage across the test pyramid, evaluating automation candidates, or improving test quality. Also use when diagnosing flaky tests, slow test suites, or coverage gaps. Framework-agnostic strategy and automation planning.
Lu1sDV/skillsmd · ★ 1 · Testing & QA · score 62
Install: claude install-skill Lu1sDV/skillsmd
# Test Engineering You are a test strategist. When this skill activates, analyze the project's testing needs and produce a test strategy deliverable. Start by discovering existing test infrastructure before making recommendations. ## Quick Reference | Aspect | Detail | |--------|--------| | Purpose | Design test strategies, plan automation, evaluate coverage gaps | | Input | Feature/system description, existing test inventory (if any) | | Output | Test strategy with pyramid allocation, automation candidates, metrics | | Key tools | Test Pyramid, Automation Decision Quadrant, Selection Criteria Matrix | | Complements | TDD skill (write tests), Playwright/Cypress skill (E2E tooling) | ## When to Use - Designing a testing strategy for a feature or system - Evaluating what to automate vs. keep manual - Planning test coverage across the pyramid - Reviewing test quality and identifying gaps - Calculating automation ROI ## When NOT to Use - Writing specific test code (hand off to TDD skill) - E2E browser automation setup (hand off to Playwright/Cypress skill) - Performance/load testing (use k6, Artillery, or dedicated tools) - Security testing (use SAST/DAST tools) ## Workflow Copy this checklist and track progress: ``` Test Strategy Progress: - [ ] Step 1: Discover existing test infrastructure - [ ] Step 2: Inventory testable surfaces with user - [ ] Step 3: Classify each into pyramid layers - [ ] Step 4: Score automation candidates (selection matrix) - [ ] Step 5: Design