From 3d43577b2dc25dfb9f666ca0e66270db799f5f66 Mon Sep 17 00:00:00 2001 From: Nelson Spence Date: Mon, 25 May 2026 15:45:29 -0500 Subject: [PATCH] docs: add a written test policy for new functionality Satisfies the OpenSSF Best Practices silver criterion test_policy_mandated: a formal written policy that tests MUST be added when major new functionality is added. Signed-off-by: Nelson Spence --- CONTRIBUTING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b146acd3..a2781369 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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)