agentleFS
gologo13gologo13/agent-skills/skills/write-unit-tests/SKILL.md

write-unit-tests

Skill0 starsChanged 9 months agoMITView on GitHub

Create comprehensive unit tests for the current code and generate the test file with proper ...; keywords: coverage, unit-test, test, error. Use only on explicit request; skip in routine implementation discussions.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 9

    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:

    Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's …

    line 10
  2. Distinctive:

    Test all public methods and functions

    line 15
  3. Distinctive:

    Test both positive and negative scenarios

    line 17
  4. Distinctive:

    Use the project's testing framework conventions

    line 20
  5. Distinctive:

    Write clear, descriptive test names

    line 21
  6. Distinctive:

    Follow the Arrange-Act-Assert pattern

    line 22
  7. Distinctive:

    Ensure tests are deterministic and repeatable

    line 31
  8. Distinctive:

    Keep tests simple and focused on one thing

    line 32
  9. Distinctive:

    Add helpful assertion messages

    line 33

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

Write Unit Tests

Overview

Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's testing conventions.

Steps

  1. Test Coverage
    • Test all public methods and functions
    • Cover edge cases and error conditions
    • Test both positive and negative scenarios
    • Aim for high code coverage
  2. Test Structure
    • Use the project's testing framework conventions
    • Write clear, descriptive test names
    • Follow the Arrange-Act-Assert pattern
    • Group related tests logically
  3. Test Cases to Include
    • Happy path scenarios
    • Edge cases and boundary conditions
    • Error handling and exception cases
    • Mock external dependencies appropriately
  4. Test Quality
    • Make tests independent and isolated
    • Ensure tests are deterministic and repeatable
    • Keep tests simple and focused on one thing
    • Add helpful assertion messages

Write Unit Tests Checklist

  • Tested all public methods and functions
  • Covered edge cases and error conditions
  • Tested both positive and negative scenarios
  • Used the project's testing framework conventions
  • Written clear, descriptive test names
  • Followed the Arrange-Act-Assert pattern
  • Included happy path scenarios
  • Included edge cases and boundary conditions
  • Mocked external dependencies appropriately
  • Made tests independent and isolated
  • Ensured tests are deterministic and repeatable

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.

Reviews can't be read right now.

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.