10 lines
1.9 KiB
Markdown
10 lines
1.9 KiB
Markdown
# Serialized modal activation observation
|
|
|
|
The first combined Unit gate recorded a single failure in Frame_TargetSwitchDuringDeferredActivation_IsSerialized: the test saw only the pending A activation when it checked for B. The first full project run passed that same test without a production change. This intermittent result required an observation review, not an assumed modal fix.
|
|
|
|
Installed bUnit2.7.2 XML documents WaitForAssertion as checking initially and whenever the component renders. ModalFrame's serialized OnAfterRender continuations can clean A and activate B through JavaScript without another component render. Therefore a JS-only invocation counter can change after the helper's initial check without triggering its next check.
|
|
|
|
The test now awaits an explicit completion source signaled by the actual newer-generation otDialog.activate invocation. It then checks the recorded calls on the renderer dispatcher. All original assertions remain: only one invocation while A is pending, exactly two after completion, increasing generation and native deactivation. A missing B invocation still fails on its five-second event timeout; this is not a sleep or timeout-padding replacement for an assertion. The await also honors the existing xUnit v3 cancellation token. No ModalFrame, shared JS, production lifecycle or behavior was changed.
|
|
|
|
The first test-only compile attempt retained as initial-analyzer.log correctly required the xUnit cancellation token (xUnit1051). That was corrected without suppressing the analyzer. The focused ModalAccessibilityTests-name filter passed127cases with0failures/0skips (tests.log/modal-observation.trx); this filter also matches related modal accessibility classes. All test commands used the owned private SQL runner. The parent retains the original failed Unit and first full-suite records under ot14-final. Final combined Unit/full acceptance remains with the primary agent.
|