RmlUi document and native lifecycle tests
Section titled “RmlUi document and native lifecycle tests”Inno.Adapter.UI.RmlUi.Tests owns the implementation assertions separated from the backend-neutral UI suite. It tests the actual RmlUi adapter, rather than replacing native defects with fake domain behavior.
Behavior and ownership
Section titled “Behavior and ownership”UiServiceTests covers the real RML frontend, importers, font family/weight selection, DOM events, hit testing, context/document/texture release and rejection of stale native handles. It uses the runtime and authoring adapters, asset import, and .NET type/serialization discovery. Font inputs come from read-only third-party samples.
Each fixture owns its temporary project, Identity scope, ModuleHost, TypeCatalog and SerializationRegistry, releasing them in dependency-reverse order. Its public test methods are discovery entries, not product extension APIs.
Required product and execution
Section titled “Required product and execution”The native-layer project requests the player product in the selected native-host environment. Use the unified plan to prepare the matching inno-ui library and dependency deployment. Missing libraries, incorrect ABI and lifecycle failures cannot be treated as passes.
A direct testhost diagnostic is valid only with those exact target/configuration/deployment prerequisites already prepared. Keep complete native assertions and the independent UI frame-context suite; a test filter cannot replace their build-dependency separation.