Runtime startup and session ownership tests
Section titled “Runtime startup and session ownership tests”Inno.Runtime.Tests owns the behavior described below. Use this guide to find relevant assertions and their environment; the scenario list is not a current passing result.
Behavior covered
Section titled “Behavior covered”Adapter catalogs freeze registration snapshots, accept open identities without creating services and reject null or duplicate providers. Presentation settings verify centered 16:9 defaults, stretch behavior and invalid-resolution rejection.
Prepared content is checked and retired before platform adapters start. Metadata copies both documents before a borrowed source can reuse its buffers. Failed metadata retires transferred module ownership; prior cancellation does not acquire borrowed content or transfer modules. Complete Player fixtures run from owned memory content without requiring a filesystem. Session log sinks retire independently, and a failing host log factory compensates startup without poisoning the host.
Sessions isolate scene and scaled/unscaled/paused time state. Script facades reject calls outside an active session. Failed startup drains before releasing factory resources; pending stop preserves dependencies and does not repeat completed owners. Required capabilities fail before allocation, optional failures propagate, and a required consumer cannot run without its failed dependency.
Static deployment freezes manifests, checks linked code identity before activation and rejects ambiguous or incomplete module closure. Generic factories do not invent discovered constructions, retained registrars cannot mutate publication, and rejected contributors retire their registrar. Static settings use contributed metadata/factories, rejecting missing factories during candidate preparation.
Environment and execution
Section titled “Environment and execution”The project declares the contract layer. Use actual module, content and session dependencies. Successful memory-backed startup is evidence for that declared fixture, not every platform, adapter or device. Keep failing-frame and pending-retirement cleanup intact.
Generate and inspect one validation plan, then execute that plan with its evaluated target, product and output properties. A focused test filter helps diagnosis; it does not replace required owner evidence. The pinned project file contains the actual references and metadata.
Scenario reference
Section titled “Scenario reference”Representative entry points are checked against the pinned source. The linked files retain all assertions and parameterized cases.
Adapter Catalog
Section titled “Adapter Catalog”Read the complete assertions. Representative entry points:
PresentationRegistrationUsesAnImmutableOpenCatalogCustomIdentitiesAreAcceptedWithoutCreatingServicesAllDomainsRejectDuplicateAndNullProvidersCapturedRegistrationsCannotBeChangedByTheirSourceCollection
Game Presentation Settings
Section titled “Game Presentation Settings”Read the complete assertions. Representative entry points:
DefaultPresentationCentersCompleteSixteenByNineFrameStretchPresentationUsesCompleteAvailableSurfacePresentationRejectsInvalidReferenceResolutionRuntimeHostRegistersDefaultPresentationProjectSetting
Player Content Source
Section titled “Player Content Source”Read the complete assertions. Representative entry points:
PreparedContentIsCheckedAndRetiredBeforeAnyPlatformAdapterStartsMetadataCopiesBothDocumentsBeforeTheBorrowedSourceCanReuseItsBuffersMetadataFailureRetiresTheTransferredModuleOwnerBeforeAnyAdapterOrContentPreparationCancellationBeforeStartupDoesNotAcquireBorrowedContentOrTransferModuleOwnership
Player Without File System
Section titled “Player Without File System”Read the complete assertions. Representative entry points:
PlayerSessionsReadOwnedMemoryContentAndRetireOnlyTheirOwnLogSinksAFailingHostLogFactoryCompensatesStartupAndKeepsTheHostUsable
Player Without File System Tests.Startup.cs
Section titled “Player Without File System Tests.Startup.cs”Read the complete assertions. Representative entry points:
CompletePlayerStartsFromOwnedMemoryAndRetiresAfterSuccessfulOrFailingFrames
Runtime Retirement
Section titled “Runtime Retirement”Read the complete assertions. Representative entry points:
FailedStartupDrainsBeforeReleasingFactoryResourcesStopHookPendingRetainsDependenciesWithoutRepeatingCompletedOwnersPendingSessionRetainsDependenciesAndCanBeRetriedThroughHost
Runtime Session
Section titled “Runtime Session”Read the complete assertions. Representative entry points:
InlineHostDeliveryPersistsSessionLogsBeforeTheProducerReturnsMultipleHostsAndSessionsKeepSceneAndTimeStateIsolatedScriptFacadesRejectCallsOutsideAnActiveSessionTimeSeparatesScaledUnscaledAndPausedProgress
Runtime Subsystem Policy
Section titled “Runtime Subsystem Policy”Read the complete assertions. Representative entry points:
MissingRequiredCapabilityRejectsBeforeFactoryAllocationSuppliedCapabilitiesAndDescriptorCollectionsAreImmutableSnapshotsOptionalUnavailabilityPropagatesToOptionalConsumersRequiredConsumerCannotRunWithoutFailedOptionalDependency
Static Deployment
Section titled “Static Deployment”Read the complete assertions. Representative entry points:
ManifestMutationCannotChangeFrozenDeploymentLinkedIdentityRejectsDifferentCodeBeforeModuleActivationClosureRejectsSharedAssemblyOwnersAndMissingUpstreamModulesCodeInputIdentityRejectsMalformedManifestData
Static Generic Factory
Section titled “Static Generic Factory”Read the complete assertions. Representative entry points:
FactoriesDoNotIntroduceClosedConstructionsIntoDiscoveryAConstructionRequiresItsOwningDeclarationRetainedRegistrarCannotMutateThePublishedCatalogFailedContributorAlsoRetiresItsRegistrar
Static Project Settings
Section titled “Static Project Settings”Read the complete assertions. Representative entry points:
SettingsUseContributedMetadataAndFactoryWithoutReflectiveDeclarationsSettingsRejectMissingFactoriesDuringCandidatePreparation
Extend safely
Section titled “Extend safely”Follow suite maintenance. Fixtures own their own sessions, temporary files and processes. Preserve thread, release and failure ordering; do not remove another owner’s lock or widen production visibility.