Skip to content

docs: formalize testing policy #25

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
JacobOptimiza merged 1 commit into from
Aug 15, 2026
Merged

docs: formalize testing policy #25

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
9 changes: 9 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down