up

docs/19_TEST_SUITE_OVERVIEW.md

@@ -42,28 +42,46 @@ contributors who need to extend coverage or diagnose failures.
 
 ---
 
-## Local runner
-
-```bash
-# minimal run: unit + property + frontend tests
-./scripts/dev-test.sh
-
-# full stack incl. Playwright and lighthouse
-./scripts/dev-test.sh --full
-````
-
-The script spins up MongoDB/Redis via Testcontainers and requires:
-
-* Docker ≥ 25
-* Node 20 (for Jest/Playwright)
-
----
-
-## CI job layout
-
-```mermaid
-flowchart LR
-  subgraph fast-path
+## Local runner
+
+```bash
+# minimal run: unit + property + frontend tests
+./scripts/dev-test.sh
+
+# full stack incl. Playwright and lighthouse
+./scripts/dev-test.sh --full
+````
+
+The script spins up MongoDB/Redis via Testcontainers and requires:
+
+* Docker ≥ 25
+* Node 20 (for Jest/Playwright)
+
+---
+
+### Feedser OSV↔GHSA parity fixtures
+
+The Feedser connector suite includes a regression test (`OsvGhsaParityRegressionTests`)
+that checks a curated set of GHSA identifiers against OSV responses. The fixture
+snapshots live in `src/StellaOps.Feedser.Source.Osv.Tests/Fixtures/` and are kept
+deterministic so the parity report remains reproducible.
+
+To refresh the fixtures when GHSA/OSV payloads change:
+
+1. Ensure outbound HTTPS access to `https://api.osv.dev` and `https://api.github.com`.
+2. Run `UPDATE_PARITY_FIXTURES=1 dotnet test src/StellaOps.Feedser.Source.Osv.Tests/StellaOps.Feedser.Source.Osv.Tests.csproj`.
+3. Commit the regenerated `osv-ghsa.*.json` files that the test emits (raw snapshots and canonical advisories).
+
+The regen flow logs `[Parity]` messages and normalises `recordedAt` timestamps so the
+fixtures stay stable across machines.
+
+---
+
+## CI job layout
+
+```mermaid
+flowchart LR
+  subgraph fast-path
     U[xUnit] --> P[FsCheck] --> I1[Testcontainer API]
   end