Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Keep Node Patrol tests out of Vitest discovery

pulse-triage[bot]8ca0208f726d
diff --git a/frontend-modern/browser-tests/README.md b/frontend-modern/browser-tests/README.md
index 42992f1c1b..b8f9e62e76 100644
--- a/frontend-modern/browser-tests/README.md
+++ b/frontend-modern/browser-tests/README.md
@@ -117,3 +117,18 @@ The separate [alert recovery checklist](alert-recovery-acceptance.md) covers
installed ordinary-event receipts, recurrence/restart isolation, and separately
identified main-build screen-reader feedback. It is a manual procedure, not an
automated runner or evidence that a candidate passed.
+
+## Patrol provider protocol tests
+
+The credential-free local provider uses Node's test runner, not Vitest. Run
+its protocol controls explicitly from `frontend-modern`:
+
+```sh
+node --test browser-tests/patrol-setup-provider.node-tests.cjs
+```
+
+The `.node-tests.cjs` name deliberately stays outside Vitest's `.test`/`.spec`
+discovery. The provider controls still execute with Node; naming them
+`.test.cjs` makes `npm test` import a second runner and fail with “No test
+suite found”, even when the protocol controls themselves pass. The browser
+journey continues to use `patrol-setup-real-backend.cjs`.
diff --git a/frontend-modern/browser-tests/patrol-setup-provider.test.cjs b/frontend-modern/browser-tests/patrol-setup-provider.node-tests.cjs
similarity index 100%
rename from frontend-modern/browser-tests/patrol-setup-provider.test.cjs
rename to frontend-modern/browser-tests/patrol-setup-provider.node-tests.cjs