Agent Skills › LanternOps/breeze › breeze-testing

breeze-testing

GitHub

Breeze项目测试编写规范，涵盖Vitest API路由、Go代理及共享验证器测试技巧。要求遵循多租户隔离、完整覆盖Happy path及错误场景等合同，确保新功能质量。

.claude/skills/breeze-testing/SKILL.md LanternOps/breeze

触发场景

编写API路由测试编写Go代理测试编写共享验证器测试检查新功能测试覆盖率

安装

npx skills add LanternOps/breeze --skill breeze-testing -g -y

更多选项

非标准路径

npx skills add https://github.com/LanternOps/breeze/tree/main/.claude/skills/breeze-testing -g -y

不安装直接使用

npx skills use LanternOps/breeze@breeze-testing

指定 Agent (Claude Code)

npx skills add LanternOps/breeze --skill breeze-testing -a claude-code -g -y

安装 repo 全部 skill

npx skills add LanternOps/breeze --all -g -y

预览 repo 内 skill

npx skills add LanternOps/breeze --list

SKILL.md

Frontmatter

{
    "name": "breeze-testing",
    "description": "Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature. Use when writing or modifying tests in this repo."
}

Breeze Testing

Project-specific conventions for writing tests. Frameworks and file placement live in CLAUDE.md; this skill covers the writing craft: patterns that catch real bugs, gotchas that burn people, and the coverage contract every new feature must satisfy.

Writing API Route Tests (Vitest)

Mock Drizzle ORM query chains matching the exact chain pattern in the source (e.g., select().from().where()).
Always test multi-tenant isolation — verify org-scoped data can't be accessed cross-org.
Test all HTTP methods, auth/authz, Zod validation failures, not-found, and error cases.
Use proper UUIDs in mock data — Zod validates UUID format and will reject 'other-org'.
Avoid trailing slashes in test URLs — Hono sub-routers return 404 for trailing slashes.
vi.mock factories are hoisted — don't reference module-level const values inside them; use literal values instead.
Read 2-3 existing test files in the same directory before writing new ones to match patterns.

Writing Go Agent Tests

Use table-driven tests for functions with multiple input/output combinations.
Always run with -race flag to catch data races.
Mock external dependencies (network, OS, filesystem) — never make real network calls.
Use build tags for platform-specific tests: //go:build !windows or //go:build darwin.
Test nil/empty inputs, error paths, and concurrency safety (spawn goroutines in tests).
Place test helpers in the same package, not in a separate _test package.

Writing Shared Validator Tests

Test valid inputs, invalid inputs, boundary values, and Zod defaults/coercion.
For discriminated unions, test each variant separately.
Test omitempty/optional fields with both present and absent values.
For schemas with superRefine, test all validation branches.

Coverage Contract — Every New Feature Must Test

Happy path — basic success case.
Auth/authz — unauthenticated, wrong role, wrong org.
Validation — missing required fields, invalid types, boundary values.
Multi-tenant isolation — cross-org access denied.
Error cases — not found, conflict, server error.
Edge cases — empty arrays, nil inputs, concurrent access.

Frameworks, file placement, and CI integration: see CLAUDE.md → Testing Standards.
Post-implementation end-to-end verification: use the feature-testing skill.