菜单
Testing patterns for Jest unit and integration tests. Use when writing tests, setting up test fixtures, or validating implementations. Jest only -- no no E2E framework. Tests live in `tests/` directory.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | testing-patterns |
| description | Testing patterns for Jest unit and integration tests. Use when writing tests, setting up test fixtures, or validating implementations. Jest only -- no no E2E framework. Tests live in `tests/` directory. |
TEMPLATE: This skill uses
{{PLACEHOLDER}}tokens. Replace with your project values before use.
Guide consistent and effective testing. Routes to existing test patterns and provides evidence templates.
// Shared test state causes flaky tests
let sharedData: any;
beforeAll(() => { sharedData = createData(); });
// Hard-coded IDs cause test pollution
const userId = "user-123";
// Isolated test state per test
beforeEach(() => {
const testData = createTestData();
});
// Unique identifiers
const userId = `user-${crypto.randomUUID()}`;
npm test # Run all tests
npx jest tests/specific-file.test.ts # Run a single test file
npx jest --testPathPattern="keyword" # Run tests matching pattern
npm test -- --coverage # Run with coverage
| Metric | Threshold |
|---|---|
| Branches | 70% |
| Functions | 80% |
| Lines | 80% |
| Statements | 80% |
tests/
├── unit/ # Fast, isolated tests
├── integration/ # API and database tests
└── setup.ts # Global test setup (if any)
**Test Execution Evidence**
**Test Suite**: [unit/integration]
**Files Changed**: [list files]
**Test Results:**
- Total Tests: [X]
- Passed: [X]
- Failed: [0]
**Coverage** (if applicable):
- Branches: X% (threshold: 70%)
- Functions: X% (threshold: 80%)
- Lines: X% (threshold: 80%)
- Statements: X% (threshold: 80%)
**Commands Run:**
```bash
npm test -- --coverage
## Reference
- **Jest Config**: `jest.config.js`
- **Test Directory**: `tests/`
- **Pattern Library**: `patterns_library/testing/`
Express API route implementation patterns with validation and error handling. Use when creating Express routes, implementing CRUD endpoints, adding server-side validation, handling webhooks, or implementing error handling. This project uses Express.js with direct pg queries -- no Next.js, no ORM.
Frontend UI patterns. DORMANT -- not currently active in a-safe-pulse (CLI + API only).
Database migration creation with mandatory RLS policies and ARCHitect approval workflow. Use when creating migrations, adding tables, or planning data migrations. Migrations are raw SQL files in `src/db/migrations/` with `XXX_description.sql` naming, registered in `index.ts`, auto-run on startup.
Pattern library discovery for pattern-first development. Use BEFORE implementing any new feature, creating components, writing API routes, or adding database operations. Ensures existing patterns are checked first.
Row Level Security patterns for database operations. Use when writing any database query, creating API routes that access data, implementing webhooks that write to the database, or working with user data. This project uses direct pg (node-postgres) queries with raw SQL -- no ORM.
Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, breaking down user stories, or translating business requirements to technical specs. Do NOT use for implementation work -- this is for planning and specification only.