Skip to content

chore: add no-source-scanning test rule to CLAUDE.md #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdalton merged 1 commit into from
Mar 26, 2026
Merged

chore: add no-source-scanning test rule to CLAUDE.md #74

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,6 +214,16 @@ Test helpers available in `test/utils/`:
- **Coverage**: `pnpm run cover`
- **NPM packages**: `node scripts/test-npm-packages.mjs` (long-running)

### Test Style — Functional Over Source Scanning

**NEVER write source-code-scanning tests**

Do not read source files and assert on their contents (`.toContain('pattern')`). These tests are brittle and break on any refactor.

- Write functional tests that verify **behavior**, not string patterns
- For modules requiring a built binary: use integration tests
- For pure logic: use unit tests with real function calls

### Vitest Memory Optimization

- **Pool**: `pool: 'forks'`, `singleFork: true`, `maxForks: 1`, `isolate: true`
Expand Down
Loading