Skip to content

docs: add a written test policy for new functionality #61

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
Navi Bot (project-navi-bot) merged 1 commit into from
May 25, 2026
Merged

docs: add a written test policy for new functionality #61

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
5 changes: 5 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@ Contributions to the code, the docs, and the paper are all welcome.
`.tvbm` / `.tvsb`) and the public method names
(`new` / `add` / `search` / `search_asymmetric*` / `top_m_candidates*` /
`write` / `load`) are stable — please don't rename them.
- **Tests are required for new functionality.** As major new functionality
is added, tests covering it MUST be added to the automated test suite
(`cargo test`, plus `pytest` for the Python bindings). Changes that add
capability without accompanying tests will be asked to add them before
merge.

## The gate (run before opening a PR — mirrors CI)

Expand Down
Loading