test: validate historian TLS migration against isolated source
This commit is contained in:
@@ -1,13 +1,54 @@
|
||||
# Validation status
|
||||
# HG issue 131 validation evidence
|
||||
|
||||
Preparation only: future patch passes `git apply --check` in the SDK 2 candidate
|
||||
checkout. Published Client/Contracts 1.0.0 package verification is pending.
|
||||
Future consumer patch validated against exact archived HG source commit
|
||||
`e4321915ebc5e0704a68ecad21b85c1cc1c80d6b`. Consumer archive base:
|
||||
`18c22cf7eb042126226e540d9b979907328055c3`. Patch SHA-256:
|
||||
`9452ee82b2bace7828a384b9f6048e9c931e8b4ec2078e0ee1baa175d0652fac`.
|
||||
|
||||
Initial primary feed query returned versions 0.4.0, 0.3.0, 0.2.0, 0.1.0 for both
|
||||
packages. HG e4321915ebc5e0704a68ecad21b85c1cc1c80d6b contains the new option under
|
||||
Unreleased; both source package version declarations still read 0.4.0. The cached
|
||||
published Client 0.4.0 exposes RequireCertificateValidation and does not expose the
|
||||
new property. Current consumer files remain on 0.4.0 and unchanged.
|
||||
## Scope and isolation
|
||||
|
||||
No issue comment/close, package publication, or HG user-checkout modification has
|
||||
been performed. Test results will be added after actual execution.
|
||||
Mode: **unreleased source project references**, not published-package verification.
|
||||
Both live package feed indexes still listed only 0.4.0, 0.3.0, 0.2.0, 0.1.0 after
|
||||
validation. Stable Client/Contracts 1.0.0 verification remains pending.
|
||||
|
||||
The user's HG checkout was only read by git archive. Only the disposable archived
|
||||
consumer Gateway csproj had its two package references replaced by project
|
||||
references into the exact archived HG source. No package was packed or published;
|
||||
no fake 1.0.0 was inserted into any feed/cache. Restore used an independent copied
|
||||
NuGet cache, isolated HTTP cache and CLI home. The normal consumer files remain
|
||||
on published 0.4.0.
|
||||
|
||||
## Actual execution
|
||||
|
||||
- Full Gateway owning project: **529 total, 523 passed, 0 failed, 6 existing live skips**.
|
||||
- Test exit **0**; repository nonzero-execution guard exit **0**.
|
||||
- All three new local wire tests passed; no new skip or expected application-result change.
|
||||
- Strict default: base HistorianGatewayException -> RpcException Status Internal ->
|
||||
HttpRequestException -> AuthenticationException, certificate-chain **UntrustedRoot**.
|
||||
The test explicitly requires the typed TLS authentication failure; RPC calls = **0**.
|
||||
- Explicit TLS opt-out: actual metadata RPC succeeds; calls = **1**.
|
||||
- Plaintext with stale opt-out and nonexistent CA path: actual metadata RPC succeeds;
|
||||
calls = **1**.
|
||||
|
||||
The first source run compiled and executed but failed one new assertion because
|
||||
it predicted the narrower HistorianGatewayUnavailableException type. The actual
|
||||
TLS exception is the public base HistorianGatewayException; the corrected assertion
|
||||
retains the required AuthenticationException graph and zero-RPC check. The fresh
|
||||
second unfiltered run above passed. The six skipped cases are the existing AVEVA
|
||||
live fixture tests; they are not a substitute for TLS wire coverage.
|
||||
|
||||
Completed UTC: `2026-11-10T19:33:17.272468+00:00`.
|
||||
Actual metadata, typed TLS exception output and binary hashes:
|
||||
`/tmp/historiangw-131-validation-20261110T193106Z/metadata-final.json`.
|
||||
Fresh second-run TRX: `/tmp/historiangw-131-validation-20261110T193106Z/test-results2`.
|
||||
Test log: `/tmp/historiangw-131-validation-20261110T193106Z/test2.log`.
|
||||
Initial failed run and restore logs are retained in the same task directory.
|
||||
|
||||
Archived-source Client DLL SHA-256:
|
||||
`87e995a43c63debdd8f648a8feb8d19d9110b45eb7b2b6906159077d90109862`.
|
||||
Archived-source Contracts DLL SHA-256:
|
||||
`ebaaa43ffc485288054eb864a59ec59264d8d9c4ea6871319fd7995192370751`.
|
||||
|
||||
No stable release was consumed by this run. The real paired 1.0.0 packages must be
|
||||
restored, the full owning suite/solution built and reviewed, and the consumer change
|
||||
landed before issue 131 is closed. No issue comment/close was performed here.
|
||||
|
||||
Reference in New Issue
Block a user