From 58b442b1aed85081d6a0d3f6cfea7ffb528dde8c Mon Sep 17 00:00:00 2001 From: Tom Boucher Date: Tue, 26 May 2026 17:17:55 -0400 Subject: [PATCH] docs(#358): clarify local test-runner guidance in CONTRIBUTING (#359) --- CONTRIBUTING.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2ef956188..ec29019f4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -688,7 +688,16 @@ node --test tests/core.test.cjs npm run test:coverage ``` -For examples of required negative matrices, parser fixtures, filesystem fault injection, security abuse tests, generated-file checks, and runtime/SDK parity tests, see [`TEST-EXAMPLES.md`](TEST-EXAMPLES.md). +For examples of required negative matrices, parser fixtures, filesystem fault injection, security abuse tests, generated-file checks, and runtime/SDK parity tests, see [`TEST-EXAMPLES.md`](./TEST-EXAMPLES.md). + +### Preferred local benchmark runner (before PR) + +When you can, run the local test bench harness before opening a PR — especially for Windows-sensitive changes. + +- Setup guide: [gsd-test-runner getting started](https://github.com/open-gsd/gsd-test-runner/blob/main/docs/getting-started.md) +- Preferred PR evidence: include the bench results summary (or artifact link) in your PR body. + +This gives maintainers a faster, higher-confidence signal than CI-only validation. ### Pre-PR Seam Checks (Manifest/Alias Routing)