Claude Skill

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creatin

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download jeffallan-claude-skills-skills_test-master-190e05a.zip · 20 KB

Install

skills CLI npx skills add https://github.com/Jeffallan/claude-skills/tree/main/skills/test-master
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install jeffallan-claude-skills@llmmart
Git git clone https://github.com/Jeffallan/claude-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole jeffallan/claude-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Test Master

Comprehensive testing specialist ensuring software quality through functional, performance, and security testing.

Core Workflow

  1. Define scope — Identify what to test and which testing types apply
  2. Create strategy — Plan the test approach across functional, performance, and security perspectives
  3. Write tests — Implement tests with proper assertions (see example below)
  4. Execute — Run tests and collect results
    • If tests fail: classify the failure (assertion error vs. environment/flakiness), fix root cause, re-run
    • If tests are flaky: isolate ordering dependencies, check async handling, add retry or stabilization logic
  5. Report — Document findings with severity ratings and actionable fix recommendations
    • Verify coverage targets are met before closing; flag gaps explicitly

Quick-Start Example

A minimal Jest unit test illustrating the key patterns this skill enforces:

// ✅ Good: meaningful description, specific assertion, isolated dependency
describe('calculateDiscount', () => {
  it('applies 10% discount for premium users', () => {
    const result = calculateDiscount({ price: 100, userTier: 'premium' });
    expect(result).toBe(90); // specific outcome, not just truthy
  });

  it('throws on negative price', () => {
    expect(() => calculateDiscount({ price: -1, userTier: 'standard' }))
      .toThrow('Price must be non-negative');
  });
});

Apply the same structure for pytest (def test_…, assert result == expected) and other frameworks.

Reference Guide

Load detailed guidance based on context:

Topic Reference Load When
Unit Testing references/unit-testing.md Jest, Vitest, pytest patterns
Integration references/integration-testing.md API testing, Supertest
E2E references/e2e-testing.md E2E strategy, user flows
Performance references/performance-testing.md k6, load testing
Security references/security-testing.md Security test checklist
Reports references/test-reports.md Report templates, findings
QA Methodology references/qa-methodology.md Manual testing, quality advocacy, shift-left, continuous testing
Automation references/automation-frameworks.md Framework patterns, scaling, maintenance, team enablement
TDD Iron Laws references/tdd-iron-laws.md TDD methodology, test-first development, red-green-refactor
Testing Anti-Patterns references/testing-anti-patterns.md Test review, mock issues, test quality problems

Constraints

MUST DO

  • Test happy paths AND error/edge cases (e.g., empty input, null, boundary values)
  • Mock external dependencies — never call real APIs or databases in unit tests
  • Use meaningful it('…') descriptions that read as plain-English specifications
  • Assert specific outcomes (expect(result).toBe(90)), not just truthiness
  • Run tests in CI/CD; document and remediate coverage gaps

MUST NOT

  • Skip error-path testing (e.g., don't test only the success branch of a try/catch)
  • Use production data in tests — use fixtures or factories instead
  • Create order-dependent tests — each test must be independently runnable
  • Ignore flaky tests — quarantine and fix them; don't just re-run until green
  • Test implementation details (internal method calls) — test observable behaviour

Output Templates

When creating test plans, provide:

  1. Test scope and approach
  2. Test cases with expected outcomes
  3. Coverage analysis
  4. Findings with severity (Critical/High/Medium/Low)
  5. Specific fix recommendations

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

Files (claude-skills)
  • references
    • automation-frameworks.md 7.2 KB
      Loading…
    • e2e-testing.md 3.3 KB
      Loading…
    • integration-testing.md 2.7 KB
      Loading…
    • performance-testing.md 2.6 KB
      Loading…
    • qa-methodology.md 6.2 KB
      Loading…
    • security-testing.md 3.3 KB
      Loading…
    • tdd-iron-laws.md 4.3 KB
      Loading…
    • test-reports.md 2.3 KB
      Loading…
    • testing-anti-patterns.md 6.4 KB
      Loading…
    • unit-testing.md 2.7 KB
      Loading…
  • SKILL.md 5.1 KB
    ---
    name: test-master
    description: Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.
    license: MIT
    metadata:
      author: https://github.com/Jeffallan
      company: https://synergetic.solutions
      version: "1.1.1"
      domain: quality
      triggers: test, testing, QA, unit test, integration test, E2E, coverage, performance test, security test, regression, test strategy, test automation, test framework, quality metrics, defect, exploratory, usability, accessibility, localization, manual testing, shift-left, quality gate, flaky test, test maintenance
      role: specialist
      scope: testing
      output-format: report
      related-skills: fullstack-guardian, playwright-expert, devops-engineer, debugging-wizard, code-reviewer, feature-forge
    ---
    
    # Test Master
    
    Comprehensive testing specialist ensuring software quality through functional, performance, and security testing.
    
    ## Core Workflow
    
    1. **Define scope** — Identify what to test and which testing types apply
    2. **Create strategy** — Plan the test approach across functional, performance, and security perspectives
    3. **Write tests** — Implement tests with proper assertions (see example below)
    4. **Execute** — Run tests and collect results
       - If tests fail: classify the failure (assertion error vs. environment/flakiness), fix root cause, re-run
       - If tests are flaky: isolate ordering dependencies, check async handling, add retry or stabilization logic
    5. **Report** — Document findings with severity ratings and actionable fix recommendations
       - Verify coverage targets are met before closing; flag gaps explicitly
    
    ## Quick-Start Example
    
    A minimal Jest unit test illustrating the key patterns this skill enforces:
    
    ```js
    // ✅ Good: meaningful description, specific assertion, isolated dependency
    describe('calculateDiscount', () => {
      it('applies 10% discount for premium users', () => {
        const result = calculateDiscount({ price: 100, userTier: 'premium' });
        expect(result).toBe(90); // specific outcome, not just truthy
      });
    
      it('throws on negative price', () => {
        expect(() => calculateDiscount({ price: -1, userTier: 'standard' }))
          .toThrow('Price must be non-negative');
      });
    });
    ```
    
    Apply the same structure for pytest (`def test_…`, `assert result == expected`) and other frameworks.
    
    ## Reference Guide
    
    Load detailed guidance based on context:
    
    <!-- TDD Iron Laws and Testing Anti-Patterns adapted from obra/superpowers by Jesse Vincent (@obra), MIT License -->
    
    | Topic | Reference | Load When |
    |-------|-----------|-----------|
    | Unit Testing | `references/unit-testing.md` | Jest, Vitest, pytest patterns |
    | Integration | `references/integration-testing.md` | API testing, Supertest |
    | E2E | `references/e2e-testing.md` | E2E strategy, user flows |
    | Performance | `references/performance-testing.md` | k6, load testing |
    | Security | `references/security-testing.md` | Security test checklist |
    | Reports | `references/test-reports.md` | Report templates, findings |
    | QA Methodology | `references/qa-methodology.md` | Manual testing, quality advocacy, shift-left, continuous testing |
    | Automation | `references/automation-frameworks.md` | Framework patterns, scaling, maintenance, team enablement |
    | TDD Iron Laws | `references/tdd-iron-laws.md` | TDD methodology, test-first development, red-green-refactor |
    | Testing Anti-Patterns | `references/testing-anti-patterns.md` | Test review, mock issues, test quality problems |
    
    ## Constraints
    
    **MUST DO**
    - Test happy paths AND error/edge cases (e.g., empty input, null, boundary values)
    - Mock external dependencies — never call real APIs or databases in unit tests
    - Use meaningful `it('…')` descriptions that read as plain-English specifications
    - Assert specific outcomes (`expect(result).toBe(90)`), not just truthiness
    - Run tests in CI/CD; document and remediate coverage gaps
    
    **MUST NOT**
    - Skip error-path testing (e.g., don't test only the success branch of a try/catch)
    - Use production data in tests — use fixtures or factories instead
    - Create order-dependent tests — each test must be independently runnable
    - Ignore flaky tests — quarantine and fix them; don't just re-run until green
    - Test implementation details (internal method calls) — test observable behaviour
    
    ## Output Templates
    
    When creating test plans, provide:
    1. Test scope and approach
    2. Test cases with expected outcomes
    3. Coverage analysis
    4. Findings with severity (Critical/High/Medium/Low)
    5. Specific fix recommendations
    
    Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions)
    
    [Documentation](https://jeffallan.github.io/claude-skills/skills/quality/test-master/)
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.