無料GitHub で公開

typescript-testing-backend

Use when writing or reviewing TypeScript backend tests — Jest unit tests for services/controllers (mocked Prisma) or Supertest integration tests against a real isolated PostgreSQL test database. Triggers on edits to `*.service.test.ts`, `*.controller.test.ts`, `*.integration.test.ts`, service/controller/API test files (`.ts`, not `.tsx`) under `**/__tests__/`, or mentions of "backend test", "service test", "API test", "database test".

LazyIsEfficient/agentic-os

インストール方法を見る

含まれるファイル（6）

SKILL.md3.3 KB
references/database-testing.md1.2 KB
references/framework-and-structure.md2.1 KB
references/integration-testing.md3.0 KB
references/mock-policy-and-quality.md1.5 KB
references/unit-testing.md1.6 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

TypeScript Testing — Backend

You are operating as a backend test engineer. Mock at the module edge for units, hit a real Postgres for integration, and never assert on internal call shapes.

Reference stack: Jest 29 with @swc/jest, Supertest for HTTP, a custom TestServer helper that simulates Next.js route handlers, and a TestDatabase helper that provisions isolated PostgreSQL instances per run with migrations + seed. Tests live co-located in __tests__/ folders.

Unit tests mock the Prisma client at the module boundary; integration tests use the real DB plus an auth-state helper for authenticated request flows.

Universal Rules

Use Jest — jest.mock() / jest.fn(), never vi.*.
Co-locate tests in __tests__/ next to the source.
Mock at the module boundary — not internal functions.
Literal expected values — expect(total).toBe(70), never expressions.
Every it() asserts observable behavior with at least one expect().
beforeEach cleanup, scoped to test-created records — never truncate seed data.
Clear auth/state helpers between tests so authenticated flows don't bleed across cases.
Never test.skip() — fix or delete.
Real DB for integration tests, mocked Prisma for unit tests.
Internal utils stay real — only mock external boundaries.

References

references/framework-and-structure.md — Jest config, test scripts, directory layout, file naming conventions, coverage
references/unit-testing.md — service unit tests with mocked Prisma, controller unit tests with injected service mocks
references/integration-testing.md — shared setup, full Supertest example, TestServer pattern, authTestHelpers API
references/database-testing.md — setupTestDatabase, isolated DBs, cleanup rules, accessing seeded data
references/mock-policy-and-quality.md — mock scope table, quality criteria, test failure triage

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

adversarial-claims-reviewer

無料

Use when adversarially reviewing a document that makes formal or technical claims — math derivations, physics papers, statistical analyses, benchmark reports, whitepapers. Inventories every equation and quantitative claim, verifies each AS NAMED in the text (never a paraphrase or a neighboring statement), and classifies VERIFIED / REFUTED / UNVERIFIABLE / VACUOUS. Triggers on "check this paper", "verify these claims", "is this derivation right", "review this proof", "audit this benchmark", "does the math hold up". For source-code review see code-review-and-quality; for skill/agent library audits see skill-library-review; for content quality scoring see content-ops.

日本語の概要は準備中です。原文の説明を表示しています。