Hexalith.FrontComposer.Testing 4.7.4

Hexalith.FrontComposer.Testing

Adopter-facing test utilities for rendering generated FrontComposer components with bUnit.

Commands support deterministic success, rejection, immediate timeout, and stall-at-Syncing. Each test host emits the same canonical ULID sequence from a fresh instance, with distinct message and correlation identifiers for every dispatch. Queries and pages accept per-request callbacks with last-write-wins configuration. TestAuthorizationEvaluator is registered as the exact evaluator exposed by the host and fails closed for unknown policies.

TestFaultEvidenceRecorder records bounded, redacted scenario evidence only; it does not inject transport behavior. Use AddFrontComposerTestHostAsync(...) for DuringHostSetup store initialization and pass its optional cancellation token when test setup is cancelable. The synchronous API rejects that mode instead of blocking on async work.

Use FrontComposerTestBase for inheritance-based tests, or call Services.AddFrontComposerTestHost(...) from a BunitContext for composition-based setup. Dispose the returned FrontComposerTestHostBuilder when composing directly so culture settings are restored. The package registers in-memory storage, deterministic tenant and user context, Shell services, command/query/page-loader fakes, loose JS interop defaults, and component assertion helpers without requiring a running app host.

The deterministic fakes are per test host instance. TestCommandService captures redacted dispatch evidence and lifecycle states, TestQueryService supports success and not-modified paths through SucceedWith<T>() and NotModifiedWith<T>(), and TestProjectionPageLoader supports configured pages plus not-modified evidence.

Evidence formatting redacts configured tenant/user values and token, secret, password, authorization, API-key, cookie, private-key, connection-string, JWT, tenant-payload, stack-trace, backend-metadata, email, phone, address, person, or full-name keyed values before truncation and assertion output. Redaction matches key names, not values, so keep personal data out of neutrally named test payload fields. Cyclic, unsupported, or throwing payloads produce a bounded <serialization-unavailable> marker without changing the configured command outcome; process-fatal exceptions still propagate. The package public surface is pinned by PublicAPI.Shipped.txt; update that baseline intentionally when adding adopter-facing APIs.

Deterministic UX assertions

Set FrontComposerTestOptions.TimeProvider to a TestTimeProvider. Its UTC clock, monotonic timestamp, one-shot timers, periodic timers, Change, and disposal advance synchronously without sleeping. Timer callbacks run outside the clock lock and use their creation execution context. Advance the clock on the component dispatcher when a timer changes rendered state. It intentionally does not drain arbitrary asynchronous work; await the operation or renderer explicitly.

UxTiming exposes canonical default budgets, including 250 ms coalescing/post-accept retry, 2 s SlowQuery, 3 s recovery notice, 10 s degradation/fresh-row lifetime, 1 s status polls, 15 s projection polls, 30 s retry cap, and the 120 s polling ceiling. UxTimingAssertions.AssertBoundary checks N-1 ms and N ms from the operation start. The consumer suite compares these defaults with Shell options and internal constants; adopter overrides do not change the canonical defaults.

Measurement and accessibility snapshots are caller-supplied, so these APIs require no browser library or TypeScript distribution. Measure the computed accessibility tree of the focusable control: Fluent UI v5 host attributes such as aria-invalid or aria-describedby do not reach the shadow input, so reading them from a bUnit host element is not browser evidence. Resolve roles and accessible names first; data-testid is a supplementary evidence locator. AssertChannel, AssertLinkedSummary, AssertState and AssertTargetSize failures name failed checks without printing measured values. Recorder missing-fact, ordinal, setup and contradicted-outcome failures name required or failed facts; non-finite and context failures describe the failed contract. Sequence diagnostics show the mismatch index, catalog row/channel labels, differing member names and counts, omitting observed copy and opaque identifiers. AssertUnobscured includes bounded, redacted measured geometry in its failure message; other helpers, including the AssertBlockedSubmit focus and AM-20 count checks, describe the failed contract. Keep the full observation sequence instead of pre-filtering unexpected messages.

For target-size exceptions, record target ordinals, exactly one UxTargetSizeExceptionKind, its UxTargetSizeRationale, the keyboard key path, neighboring bounds for Spacing ([] is a measured empty inventory; null is unmeasured and fails AssertTargetSize and Passed AE-04 packets), or a separate conforming equivalent-control ordinal and bounds for Equivalent. The fixed schema excludes credentials, AX names, tenant payloads, backend metadata, stack traces, and personal text. Do not encode identifiers in numeric measurement fields. Increase MaxDiagnosticPayloadCharacters when a complete structured measurement packet is needed; truncation remains explicit.

These helpers record automated evidence only. They do not replace required manual assistive-technology/device evidence or close OI-16, G-4, FLUENT-APP-1, or Product approval.