Reference intent and recovery tests
Section titled “Reference intent and recovery tests”Inno.References.Tests verifies the References contracts through their public entry points. Use this page to locate relevant assertions; it is not a report that these tests passed for your current change.
Behavior covered
Section titled “Behavior covered”Read scopes resolve only their captured generation, freeze identities and revoke on disposal without owning the root or allocator. Catalog tests preserve unassigned and Missing intent and reject duplicate reference kinds. Recovery resolves after objects exist, compensates attempted owners around publication and rolls back applied participants in reverse order. Pending retirement keeps owners protected; ordinary cleanup failure cannot pretend that an irreversible publication was rolled back.
Environment and execution
Section titled “Environment and execution”The project declares the contract validation layer. Use the shared validation workflow to select its actual dependencies and environment. Inspect the pinned project file for package and project references.
A focused diagnostic from the engine root is:
dotnet test tests/references/Inno.References.Tests/Inno.References.Tests.csproj --configuration Debug --disable-build-servers -m:1 -nodeReuse:falseUse --filter FullyQualifiedName~MethodName to investigate one case. A filtered run does not replace the obligations in the validation plan. Restore the declared SDK, packages and any tool/process prerequisites before executing; preserve cancellation, thread and cleanup requirements.
Scenario reference
Section titled “Scenario reference”These representative methods are preserved from the original reference and checked against the pinned source. The linked files contain all assertions and parameterized cases.
Content Read Scope
Section titled “Content Read Scope”Read the assertions. Representative entry points:
ScopeResolvesOnlyCapturedGenerationAndRevokesOnDisposeScopeDoesNotOwnRootOrAllocatorAndFreezesIdentitiesDetachedDuplicateAndUnknownActiveRootsAreRejected
Reference Catalog
Section titled “Reference Catalog”Read the assertions. Representative entry points:
Resolve_PreservesUnassignedAndMissingIntentCreate_RejectsDuplicateReferenceKindsRecoveryTransaction_RollsBackAppliedParticipantsInReverseOrderRecoveryResolvesOnlyAfterObjectsExistAndRetainsNeutralResultsAfterCommit
Reference Recovery
Section titled “Reference Recovery”Read the assertions. Representative entry points:
CandidateFailureCompensatesAttemptedOwnersAroundPublicationPendingRetirementKeepsOwnersAndFaultsTheSharedGateOrdinaryCleanupFailureStillRetiresOtherOwnersAndCannotPretendToRollbackEarlierParticipantFailureIsRetainedAlongsidePendingOwnership
Extend safely
Section titled “Extend safely”Follow the shared suite-maintenance guidance. Preserve this suite’s owner-thread, resource-release and failure assertions when adding cases.