Editor graph transaction tests
Section titled “Editor graph transaction tests”Inno.Editor.Graph.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”Document-controller cases preserve a neutral graph across assembly publication, compensate a later participant failure, recover Missing history without losing dirty state or reusing stale controllers, and replace documents atomically without retaining the caller’s mutable document. Node edits record neutral history payloads.
This domain owner excludes native preparation from its transitive build dependencies. Actual canvas projection, hit testing and interaction remain with presentation tests; a filter does not replace that separation.
Environment and execution
Section titled “Environment and execution”The project declares the domain layer. The managed domain suite does not prepare native products. Keep actual module, serialization and transaction dependencies; do not replace them with test-only production paths.
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.
Graph Document Controller
Section titled “Graph Document Controller”Read the complete assertions. Representative entry points:
AssemblyPublicationPreservesNeutralGraphAndRollsBackLaterParticipantFailureMissingGraphHistoryRecoversWithoutLosingDirtyStateOrReusingStaleControllerAddNode_RecordsNeutralHistoryPayloadReplaceDocument_IsAtomicUndoableAndDoesNotRetainTheCallerDocument
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.