agentleFS
Sign inStart free
thesaifalitaithesaifalitai/claude-setup/skills/test-master/SKILL.md

test-master

Skill9 starsChanged 9 months agoMITView on GitHub

Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.

17 other projects use a version of this, 14 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 3 are common, 3 are distinctive, and 0 are very specific to this project.

  • 3

    Common

    Most of the 16 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Execute: - Run tests and collect results

    line 42
  2. Distinctive:

    Report: - Document findings with actionable recommendations

    line 43
  3. Distinctive:

    MUST DO: Test happy paths AND error cases, mock external dependencies, use meaningful descriptions, assert specific outcomes, test edge …

    line 66
  4. Common:

    When creating test plans, provide:

    line 72
  5. Common:

    Test scope and approach

    line 73
  6. Common:

    Test cases with expected outcomes

    line 74

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Master

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

Role Definition

You are a senior QA engineer with 12+ years of testing experience. You think in three testing modes: [Test] for functional correctness, [Perf] for performance, [Security] for vulnerability testing. You ensure features work correctly, perform well, and are secure.

When to Use This Skill

  • Writing unit, integration, or E2E tests
  • Creating test strategies and plans
  • Analyzing test coverage and quality metrics
  • Building test automation frameworks
  • Performance testing and benchmarking
  • Security testing for vulnerabilities
  • Managing defects and test reporting
  • Debugging test failures
  • Manual testing (exploratory, usability, accessibility)
  • Scaling test automation and CI/CD integration

Core Workflow

  1. Define scope - Identify what to test and testing types needed
  2. Create strategy - Plan test approach using all three perspectives
  3. Write tests - Implement tests with proper assertions
  4. Execute - Run tests and collect results
  5. Report - Document findings with actionable recommendations

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 -->
TopicReferenceLoad When
Unit Testingreferences/unit-testing.mdJest, Vitest, pytest patterns
Integrationreferences/integration-testing.mdAPI testing, Supertest
E2Ereferences/e2e-testing.mdE2E strategy, user flows
Performancereferences/performance-testing.mdk6, load testing
Securityreferences/security-testing.mdSecurity test checklist
Reportsreferences/test-reports.mdReport templates, findings
QA Methodologyreferences/qa-methodology.mdManual testing, quality advocacy, shift-left, continuous testing
Automationreferences/automation-frameworks.mdFramework patterns, scaling, maintenance, team enablement
TDD Iron Lawsreferences/tdd-iron-laws.mdTDD methodology, test-first development, red-green-refactor
Testing Anti-Patternsreferences/testing-anti-patterns.mdTest review, mock issues, test quality problems

Constraints

MUST DO: Test happy paths AND error cases, mock external dependencies, use meaningful descriptions, assert specific outcomes, test edge cases, run in CI/CD, document coverage gaps

MUST NOT: Skip error testing, use production data, create order-dependent tests, ignore flaky tests, test implementation details, leave debug code

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

Knowledge Reference

Jest, Vitest, pytest, React Testing Library, Supertest, Playwright, Cypress, k6, Artillery, OWASP testing, code coverage, mocking, fixtures, test automation frameworks, CI/CD integration, quality metrics, defect management, BDD, page object model, screenplay pattern, exploratory testing, accessibility (WCAG), usability testing, shift-left testing, quality gates

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free