Files
scadaproj/components/ui-theme/validation/bunit-2.7.2/HistorianGateway/VALIDATION.md
T
2026-11-13 15:32:41 -05:00

2.1 KiB

BU-08 HistorianGateway validation

Existing checkout execution was explicitly authorized on 2026-11-13 after the managed-worktree service stalled. Pending creation cell g7:39 was terminated; source checkout was clean at 8d6f2f6 and switched from main to codex/scada-ui-consistency before mutation.

Results

  • Before full suite: 1509 total, 1433 passed, 1 failed, 75 skipped. The sole pre-existing CorporateFqdnGuard failure was fixed separately by parent commit 2bbe3a0 (deployment-doc hostname policy); the guard and tests were not changed.
  • bUnit migration: exact 2.7.2 and direct AngleSharp 1.5.2; xUnit 2.9.3/test SDK/runner preserved. Seven dashboard fixtures migrate only context/render/auth API and auth-double names; assertions and production callbacks are unchanged.
  • Focused Dashboard: 71 passed, zero failed/skipped.
  • After clean Release build/forced restore full suite: 1509 total, 1434 passed, zero failed, 75 skipped. Same 1509 identities; no added/removed identities and no new skips. The only changed outcome is the separate CorporateFqdnGuard prerequisite correction.
  • Package vulnerability audit: no vulnerable packages. Actual graph has bunit/2.7.2, AngleSharp/1.5.2 and no old bunit.core/web generation. Production project asset graphs contain no newly leaked bUnit/AngleSharp/xUnit dependency.
  • No Theme/UI/production implementation, runtime configuration changes or historian writes were performed. Parent reviewed and committed the migration as 1be3f5e.

Existing runtime limitations

The 75 inherited skips require explicitly configured live Historian/Windows/Galaxy/integration fixtures. Their identities are unchanged in test-comparison.json and their source skip guards remain unchanged. They are NOT runtime passes and remain an explicit GB applicability decision for the parent; no fixtures were bypassed or skips added.

Evidence

Before/after metadata records exact commands and starting HEAD/status; before/after TRX and discovery logs preserve identities/outcomes; package/audit logs and selected resolved-library JSON record the dependency graph. Parent hostname correction commit is noted above so its effect is not attributed to bUnit.