Play Mode and Console behavior tests
Section titled “Play Mode and Console behavior tests”Inno.Editor.PlayMode.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”Play entry waits for compilation and can be canceled before scripts are ready. Failure returns to Edit without replacing scenes; pending stop retains history and blocks a new generation until work drains. Exit restores editing history.
Input tests preserve pointer bounds even after consumption, keep captured input isolated by window, disarm on window exit and route game input only after Editor consumption. Console tests preserve distinct native card identities and uniform spacing. Popup tests cover content-width search, downward selectors and panel bounds.
Clear-on-Play and manual history clear preserve current diagnostics until their causes resolve. Completed sessions retain every runtime severity; failed entry keeps preparation diagnostics because simulation never started.
Daily native behavior and lifecycle contracts belong here; ten-thousand-row scale measurements belong to Editor performance tests. Both use the same Inno.Testing.Editor.Native fixture rather than copied lifecycle implementations.
Environment and execution
Section titled “Environment and execution”The project declares the contract layer. Prepare the selected Editor native product and deployment through the plan. This owner declares successful results non-reusable across runs. Disable automatic imgui.ini output; persistence scenarios own temporary state rather than writing into compilation output.
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.
Console Entry Layout
Section titled “Console Entry Layout”Read the complete assertions. Representative entry points:
DistinctEntryDomainsDoNotReuseImGuiCardIdentityCollapsedCardsUseOneUniformNativeItemSpacing
Console Panel Native Layout
Section titled “Console Panel Native Layout”Editor Game Input Capture
Section titled “Editor Game Input Capture”Read the complete assertions. Representative entry points:
ConsumedMouseMovementStillUpdatesPointerBoundsConsumedMouseMovementDoesNotReleaseCapturedInputOrChangeOtherWindowsWindowExitDisarmsCaptureBeforeItsFirstDeliveredInputDispatcherRoutesInputOnlyAfterEditorConsumption
Editor Play Mode
Section titled “Editor Play Mode”Read the complete assertions. Representative entry points:
EntryWaitsForCompilationAndExitRestoresEditingHistoryPendingStopRetainsHistoryAndBlocksNewGenerationUntilWorkDrainsCompilationFailureReturnsToEditWithoutReplacingScenesEnteringPlayCanBeCancelledBeforeScriptsBecomeReady
Editor Popup Layout
Section titled “Editor Popup Layout”Read the complete assertions. Representative entry points:
ContextMenuSearchUsesCompletePopupContentWidthTwoItemSelectorOpensBelowControlWithoutOverflowLongSelectorNearWindowBottomScrollsWithoutOpeningUpwardSelectorInsideLayoutChildUsesContainingPanelBounds
Play Mode Log Retention
Section titled “Play Mode Log Retention”Read the complete assertions. Representative entry points:
ClearOnPlayRemovesOldLogsButRetainsCurrentDiagnosticsManualClearRemovesHistoryButKeepsCurrentIssuesUntilResolvedCompletedPlaySessionRetainsEveryRuntimeSeverityFailedEntryRetainsPreparationDiagnosticsBecauseSimulationNeverStarted
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.