docs(tests): IntegrationTests-033 resolved: Write2 live smoke passed on windev (#212)
ci / nightly-windev (push) Has been skipped
ci / windows-x86 (push) Successful in 2m2s
ci / java (push) Failing after 4m44s
ci / portable (push) Failing after 9m25s

Ran the Write2 live smoke on windev against origin/main 04a40f2c (x86 Release
worker, item TestChildObject.TestInt). It passed: Ok, hresult 0, and a matching
OnWriteComplete. MXAccess reported SecurityError/1008 on the completion, which
is the Galaxy refusing an unauthenticated write; plain Write got the same
status and the value did not change. Corrected the test comment that said the
reply meant the write succeeded.

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 20:26:33 -05:00
parent 04a40f2c1a
commit ebbfaa4c03
3 changed files with 11 additions and 5 deletions
@@ -306,9 +306,13 @@ public sealed class WorkerLiveMxAccessSmokeTests(ITestOutputHelper output)
new TestServerCallContext()).ConfigureAwait(false);
LogReply("Write2", writeReply);
// Happy-path Write2: the worker reached the COM Write2 call and it
// succeeded. InvalidRequest here means the executor rejected the
// payload (missing value/timestamp) before reaching MXAccess.
// Ok means the worker reached the COM Write2 call and COM accepted it.
// InvalidRequest here means the executor rejected the payload
// (missing value/timestamp) before reaching MXAccess. Ok does not
// mean the provider applied the value: on the windev Galaxy the
// default item is security-classified, so the completion carries
// SecurityError/1008 (an unauthenticated write refused; Write2 has
// no user id). Plain Write gets the same status (#212, 2026-11-12).
Assert.Equal(ProtocolStatusCode.Ok, writeReply.ProtocolStatus.Code);
Assert.Equal(MxCommandKind.Write2, writeReply.Kind);