From 9d124fc41e0a5498b051061050827d1b1b66d86c Mon Sep 17 00:00:00 2001 From: Jacob Date: Sat, 15 Aug 2026 09:24:19 +0200 Subject: [PATCH] docs: formalize testing policy --- CONTRIBUTING.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8b6c0f4..9eeb469 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,6 +36,15 @@ The repository also fuzzes the `config.tsv` parser with ClusterFuzzLite on pull requests that affect its Rust source or fuzzing integration. Fuzzing is a supplement to, not a replacement for, the ordinary test suite. +## Testing policy + +Major new functionality must include appropriate automated tests for its new +behavior. Bug fixes must include regression tests when reasonably practical. +Add or update the applicable existing suite for the component you change: +Rust, PowerShell/Pester, or the npm bootstrap. All applicable tests must pass +in CI before merge. Documentation-only changes and changes that do not alter +behavior do not need new tests. + Use a focused branch and pull request, wait for CI, and squash merge only after the applicable checks pass. New Actions references must use full commit SHAs.