A testing guide for Vitest unit tests and end-to-end tests. Vitest is a JavaScript and TypeScript test runner; end-to-end tests check the complete system through its real MCP server, and TDD means writing tests to guide development.

Use it to write or fix unit tests, end-to-end tests, fixtures, seed data, and test coverage checks.

It helps catch errors against a real SQLite database and real server communication instead of relying on test doubles.

How seasonedcc/discord-manager configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to seasonedcc/discord-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/seasonedcc/discord-manager/main/.claude/skills/testing/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/seasonedcc/discord-manager

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/seasonedcc/discord-manager/testing/github.svg)](https://agentmods.dev/skills/seasonedcc/discord-manager/testing)

Your own site

<a href="https://agentmods.dev/skills/seasonedcc/discord-manager/testing"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/seasonedcc/discord-manager/testing"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,378 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00101	$0.04378
Opus 5.5	$0.00040	$0.01751
Sonnet 5.5	$0.00020	$0.00876
Haiku 4.5	$0.00010	$0.00438

Measured 2mo ago against content hash 3a68b854a2cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/testing/SKILL.md · 230 lines

How it starts

The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing

Everything here documents the repository as it is on main. If main disagrees with this file, main wins: follow it and flag the drift.

Two suites and a standing gate. Unit tests exercise business functions against a real SQLite database with no mocks. End-to-end specs drive the real MCP server over stdio, seeded through the real ingestion functions by a scripted fake gateway feed. The dev-seed coverage gate proves every registered tool answers with demo state from a freshly dev-seeded store.

Commands

pnpm run test:unit           # every unit test, TZ=UTC
pnpm run test:e2e            # the E2E specs, then the tool coverage gate
pnpm run test:seed-coverage  # every tool answers from a freshly dev-seeded store
pnpm run test                # unit, E2E, then the seed-coverage gate
pnpm run lint
pnpm run tsc

Always run lint, tsc, and test:unit before opening a PR. Run the E2E specs a change directly touches; a change to the seed, the client harness, or the runner touches every spec, so there the whole suite is the directly-touched set. Run test:seed-coverage whenever a change touches the dev seed, registers or renames a tool, or reshapes what a tool answers.

To run a subset, pass arguments straight to pnpm run test:e2e with no -- separator: positional arguments filter specs by filename substring, and --repeat=<n> reruns the filtered set — pnpm run test:e2e waiting-for-activity --repeat=2. The runner is tests/run-e2e.ts; the tool coverage gate only judges a full, unfiltered run.

Test-driven development

For a bug or a new behavior, follow Red-Green-Refactor:

Red — write a test that reproduces the issue or states the new behavior. It must fail.
Green — implement the minimum that makes it pass.
Refactor — clean up with everything still green.

Mutation proofs

A green suite proves nothing about a specific test until that test has been seen red for the right reason. When the code under test already exists — a fix being re-verified, a regression test over already-correct code — red-first is not natural, so substitute a mutation proof:

Read the full file on GitHub · 230 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 230 lines · 101 tokens per session scan A 3a68b854a2cf

Subscribe to this mod's changes

testing is a skill published in the GitHub repository seasonedcc/discord-manager (3 stars, last pushed 2d ago), licensed MIT. It adds 101 tokens to every session and 4,378 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

E2E testing Testing Unit testing

testing next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
testingseasonedcc/discord-manager	Skill	3	2d ago	MIT	A	101	Claude Code
test-masterJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	104	Claude Code
axiom-testingCharlesWiltgen/Axiom	Skill	1.3k	yesterday	MIT	A	38	Claude Code
test-generatorrshankras/claude-code-apple-skills	Skill	864	2d ago	MIT	A	33	Claude Code
testing-blocksadobe/skills	Skill	319	yesterday	Apache-2.0	A	61	Claude Code
designing-testsCloudAI-X/claude-workflow-v2	Skill	1.4k	1mo ago	MIT	A	48	Claude Code
test-automation-expertcuriositech/some_claude_skills	Skill	263	yesterday	MIT	A	133	Claude Code

discord-manager: Skill for Claude Code