Skip to content
Agentmart
Submit a tool

writing-tests

Rules for deciding what is worth testing.

Skill by mister-gnommer

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/mister-gnommer-writing-tests

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Rules for deciding what is worth testing. Use when writing or editing tests in any language.

Use cases: testing, writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/writing-tests

What's inside

Skill name
writing-tests
Description
Rules for deciding what is worth testing. Use when writing or editing tests in any language.
License
MIT
Instructions
18 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Writing tests

Every test must be able to fail because of a realistic bug you can name. If you can't name one, don't write the test.

## Don't test
- Mocks: asserting a mocked value comes back unchanged.
- The language, runtime or libraries: that `if`, `map` or the framework works.
- Trivial code: getters, constants, pass-through wrappers, plain data shapes.

## Do test
- Business logic, branching, edge cases (empty, boundary, error paths).
- Bug fixes: one regression test that reproduces the bug.
- Contracts at module boundaries.

## Size
A few meaningful tests beat exhaustive coverage. Match the project's existing test density. If a case is borderline, skip it and mention it instead.

From mister-gnommer/rules-of-engagement, MIT.

More from mister-gnommer/rules-of-engagement

Signals

Stars
0
Forks
0
Open issues
4
Last commit (this folder)
Oct 3, 2026 (27 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from mister-gnommer

Cite this page

writing-tests skill. Agent Mart. https://agentmart.dev/skills/mister-gnommer-writing-tests (last updated 2026-10-24)