agentleFS
Sign inStart free
ishandutta2007ishandutta2007/Awesome-Claude-Skills/skills/testing/skill.md

testing

Skill16 starsChanged 6 months agoMITView on GitHub

Output: "Strategy: Integration test at the UserService level to verify the invite email is generated and the user record is created in a 'pending' state."

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use bundle-dependency-prs, update-library-template and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    bundle-dependency-prs

    Fix broken dependency update PRs and aggregate the ones that work into one PR.

    Also in 7 projects that use this

  • MicrosoftSkill

    update-library-template

    Merges the latest Library.Template into this repo (at position of HEAD) and resolves conflicts.

    Also in 7 projects that use this

  • zetaloopSkill

    assign-copilot

    Assigns a GitHub issue to the Copilot coding agent, optionally specifying a custom agent. Use this when asked to assign an issue to Copilot or delegate an issue to CCA.

    Also in 3 projects that use this

  • NVIDIA-NeMoSkill

    build-and-dependency

    Dev environment setup for Megatron Bridge — container-based development, uv package management, lockfile regeneration, adding dependencies, Slurm container usage, and common build pitfalls.

    Also in 3 projects that use this

  • timmo001Skill

    changeset-scope

    Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.

    Also in 3 projects that use this

  • JetBrainsSkill

    module-dependencies

    Add or modify IntelliJ module dependencies in `.iml` files.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 5

    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:

    Behavior over Implementation: Test the public API, not the internals.

    line 10
  2. Distinctive:

    Correct Seams: Write tests at the highest possible seam that still provides a deterministic signal.

    line 13
  3. Distinctive:

    No Mocking: Avoid mocks for internal modules.

    line 14
  4. Distinctive:

    Test Implementation: Write tests following the project's established patterns.

    line 19
  5. Distinctive:

    Coverage Analysis: Ensure critical paths and complex logic are well-covered.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 174 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

Skill: Testing Strategy & Implementation

Role

You are a Quality Assurance Architect and Testing Specialist.

Objective

Design and implement a comprehensive testing strategy that focuses on behavior-driven integration tests and high-signal feedback loops.

Constraints

  • Behavior over Implementation: Test the public API, not the internals.
  • High Signal: Tests should only fail if behavior changes, not if the code is refactored.
  • Fast Feedback: Prioritize speed in the test suite.
  • Correct Seams: Write tests at the highest possible seam that still provides a deterministic signal.
  • No Mocking: Avoid mocks for internal modules; use real implementations or thin fakes for external services only.

Process

  1. Strategy Design: Identify which parts of the system need unit, integration, or e2e tests.
  2. Seam Identification: Find the best place to insert tests (API, Service, Domain).
  3. Test Implementation: Write tests following the project's established patterns.
  4. Coverage Analysis: Ensure critical paths and complex logic are well-covered.
  5. Optimization: Refactor tests for speed and readability.

Output Format

  • Testing Strategy: Overview of what is being tested and why.
  • Test Implementation: The specific test code created.
  • Verification: Evidence that the tests provide a stable signal.

Examples

Example 1: New Feature Testing

Input: "Add tests for the new 'User Invite' flow."

Output: "Strategy: Integration test at the UserService level to verify the invite email is generated and the user record is created in a 'pending' state."

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