Skip to content

docs: add test directory convention to AGENTS.md #7993

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

Open
delock wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −0
Open

docs: add test directory convention to AGENTS.md #7993

Show file tree
Hide file tree
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
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@
- Write beginner-friendly code: avoid deeply nested expressions or chained logic. Break complex expressions into clear, named intermediate steps.
- Comments should explain **why**, not **what**. Describe the purpose and reasoning, not the mechanics that the code already shows.
- New features must include corresponding tests and documentation updates.
- New tests must go under `tests/unit/v1/` (not `tests/unit/`), since the GPU CI workflow only runs `tests/unit/v1/`. Other workflows (cpu, inference) may run tests from `tests/unit/` as well.

## Tool Caveats

Expand Down
1 change: 1 addition & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@
- Write beginner-friendly code: avoid deeply nested expressions or chained logic. Break complex expressions into clear, named intermediate steps.
- Comments should explain **why**, not **what**. Describe the purpose and reasoning, not the mechanics that the code already shows.
- New features must include corresponding tests and documentation updates.
- New tests must go under `tests/unit/v1/` (not `tests/unit/`), since the GPU CI workflow only runs `tests/unit/v1/`. Other workflows (cpu, inference) may run tests from `tests/unit/` as well.

## Tool Caveats

Expand Down
Loading