vitest-testing

A server-side testing reference for Vitest, a JavaScript and TypeScript test runner, in the apps/server package. It covers databases, Socket.IO connections, command-line processes, asynchronous code, and fake timers.

In plain words
What is it for?
Use it when writing or changing server tests, testing SQLite database code or Socket.IO servers, choosing mocks, handling asynchronous behavior, or using fake timers.
Why use it?
It gives consistent patterns for isolating tests and cleaning up databases, servers, and connections. This helps prevent test failures caused by shared state or leaked ports.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/recca0120/code-quest/vitest-testing
Any agent
npx skills add recca0120/code-quest --skill vitest-testing
Clone the repo
git clone --depth 1 https://github.com/recca0120/code-quest

Made for: Claude Code, Codex.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,266 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00068 $0.03266
Opus 5 $0.00034 $0.01633
Sonnet 5 $0.00014 $0.00653
Haiku 4.5 $0.00007 $0.00327

Measured 2d ago against content hash 10670797194f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vitest-testing scanned grade A with 1 finding 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 2d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

| 5 | **vi.mock** | 整個模組替換 | 無法 inject 的依賴(`child_process`、`node-pty`、`fs/promises`) |
.claude/skills/vitest-testing/SKILL.md · 328 lines

How it starts

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

Vitest Testing — Server Reference

⚠️ This skill is server-focused. Frontend tests follow frontend-testing (Testing Library + six core principles). This file covers DB / socket.io server-side / CLI process patterns only.

Stack: vitest 4.x, TypeScript, ESM, better-sqlite3, socket.io-client


Test Organization

  • One test file per source file: foo.tssrc/__tests__/foo.test.ts
  • Use describe to group by class or feature; it for individual behaviors
  • Name tests as behavior assertions: 'creates a session with a unique id'
describe('MyService', () => {
  it('returns null when not found', () => { ... });
  it('throws when input is invalid', () => { ... });
});

Setup / Teardown

  • beforeEach — use for state that must be fresh per test (DB, server, sockets)
  • beforeAll — use only for truly shared, read-only fixtures (e.g. static config)
  • Always clean up servers and connections in afterEach to prevent port leaks

In-memory SQLite pattern (DB tests):

beforeEach(() => {
  db = createDatabase(':memory:');
  migrate(db, { migrationsFolder });
  store = new DrizzleSessionStore(db, sessions);
});

Socket.io integration pattern:

beforeEach(async () => {
  httpServer = createServer();
  io = new Server(httpServer);
  handler.register(io);
  await new Promise<void>((r) => httpServer.listen(0, r));
  const { port } = httpServer.address() as AddressInfo;
  clientSocket = ioc(`http://localhost:${port}`, { transports: ['websocket'] });
  await new Promise<void>((r) => clientSocket.on('connect', r));
});

afterEach(async () => {
  clientSocket.disconnect();
  io.close();
  await new Promise<void>((r) => httpServer.close(r));
});

Test Double 選擇(server)

優先選低層級 double(真實實作接近度高 → 測試信心高):

層級 方式 用途 範例
1 真實實作 可用 in-memory / 真的 server/socket 時優先 :memory: SQLite、真的 http.createServer + socket.io server、real repositories
2 Spy 觀察真實方法呼叫但不改行為 vi.spyOn(logger, 'warn') — 方法照跑,可驗證被呼叫
3 Fake 保留行為的簡化實作(共用 harness) createFakeSummoner().claude() / FakeSummoner — 見 fake-summoner-server / fake-summoner-client skill;in-memory DrizzleSessionStore
4 Stub 固定回傳值,無邏輯 vi.fn().mockResolvedValue(fixedResult) — 窄介面、純 query
5 vi.mock 整個模組替換 無法 inject 的依賴(child_processnode-ptyfs/promises

Read the full file on GitHub · 328 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.

  1. 2d ago First seen · 328 lines · 68 tokens per session scan A 10670797194f

Subscribe to this mod's changes

vitest-testing is a skill published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 3,266 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens