test-optimization-patterns

A set of patterns for making automated tests run faster. It covers database setup, file and external-service substitutes, test data, asynchronous waits, test size, and running tests at the same time.

In plain words
What is it for?
Use it when refactoring a slow test suite, especially tests that reset database data, perform file or API operations, repeat setup, or could run independently.
Why use it?
Slow tests often spend time repeatedly writing to databases, reading files, calling outside services, or waiting unnecessarily. These patterns show ways to reduce that overhead while noting possible risks.

Command

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 commands/classmethod/tsumiki/test-optimization-patterns
Clone the repo
git clone --depth 1 https://github.com/classmethod/tsumiki
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,330 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00026 $0.05330
Opus 5 $0.00013 $0.02665
Sonnet 5 $0.00005 $0.01066
Haiku 4.5 $0.00003 $0.00533

Measured yesterday against content hash 584d95839093, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-optimization-patterns 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 yesterday.

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.

commands/test-optimization-patterns.md · 744 lines

How it starts

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

テスト最適化パターン集

テスト実行速度を改善するためのリファクタリングパターンとベストプラクティスをまとめたドキュメントです。

パターン一覧

パターン 効果 難易度 リスク
1. データベーストランザクション ★★★★★
2. ファイルI/Oのモック化 ★★★★★
3. 外部APIのモック化 ★★★★★
4. beforeEach → beforeAll ★★★☆☆
5. 非同期待機の最適化 ★★★☆☆
6. テストデータファクトリー ★★☆☆☆
7. テストの粒度見直し ★★★☆☆
8. 並列実行可能な設計 ★★★☆☆

パターン1: データベーストランザクション

概要

各テストでデータベースのクリア・再投入を行うと、I/O待機時間が累積して遅くなります。トランザクションを使ってロールバックすることで、物理的なDELETE/INSERTを避けて高速化できます。

適用条件

  • ✅ beforeEach でデータのクリア・再投入を行っている
  • ✅ テストごとにクリーンな状態が必要
  • ✅ データベースがトランザクションをサポート

Before(遅い実装)

describe('User API', () => {
  beforeEach(async () => {
    // 毎回DELETE・INSERT(遅い)
    await db.query('DELETE FROM users');
    await db.query('DELETE FROM posts');
    await db.query('INSERT INTO users (id, name) VALUES (1, "Test")');
    await db.query('INSERT INTO posts (id, user_id, title) VALUES (1, 1, "Post")');
  });

  afterEach(async () => {
    await db.disconnect();
  });

  it('should get user', async () => {
    const user = await getUserById(1);
    expect(user.name).toBe('Test');
  });

  it('should get posts', async () => {
    const posts = await getPostsByUserId(1);
    expect(posts).toHaveLength(1);
  });
});

After(高速実装)

describe('User API', () => {
  let transaction;

  beforeEach(async () => {
    // トランザクション開始
    transaction = await db.transaction();

    // データ準備(トランザクション内)
    await transaction.query('INSERT INTO users (id, name) VALUES (1, "Test")');
    await transaction.query('INSERT INTO posts (id, user_id, title) VALUES (1, 1, "Post")');
  });

  afterEach(async () => {
    // ロールバック(高速)
    await transaction.rollback();
  });

  it('should get user', async () => {
    const user = await getUserById(1);
    expect(user.name).toBe('Test');
  });

  it('should get posts', async () => {
    const posts = await getPostsByUserId(1);
    expect(posts).toHaveLength(1);
  });
});

Read the full file on GitHub · 744 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. yesterday First seen · 744 lines · 26 tokens per session scan A 584d95839093

Subscribe to this mod's changes

test-optimization-patterns is a command published in the GitHub repository classmethod/tsumiki (974 stars, last pushed 25d ago), licensed MIT. It adds 26 tokens to every session and 5,330 once invoked, about $0.0001 per session on Opus 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-30.