File ownership and publication tests
Section titled “File ownership and publication tests”Inno.Core.IO.Tests verifies the IO 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”The suite covers absent versus empty documents, immutable read-only bytes, independent reader protection, timeout/cancellation ownership, complete payload replacement, same-directory staging and path traversal rejection. Owned stream tests close the reader before its independent owner and preserve retryable release.
Environment and execution
Section titled “Environment and execution”The project declares the domain validation layer. Use the shared validation workflow to select its actual dependencies and environment. Inspect the pinned project file for package and project references.
Windows directory-sharing, cancellation and rollback cases carry SupportedOSPlatform("windows"). An early return or skip on another host is not evidence that the Windows contract passed.
A focused diagnostic from the engine root is:
dotnet test tests/core/Inno.Core.IO.Tests/Inno.Core.IO.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.
Byte Document Store
Section titled “Byte Document Store”Read the assertions. Representative entry points:
ReadOnlyDocumentsOwnBytesAndRejectReplacementFilesDistinguishAbsentAndEmptyAndReplaceCompleteDocuments
File Lease
Section titled “File Lease”Read the assertions. Representative entry points:
ReadersShareOwnershipAndExcludeWritersUntilEveryReaderClosesCompetingOwnershipWaitsForDisposalAndRetainsTheSameLeaseFileTimeoutAndCancellationDoNotReleaseAnotherOwnerInvalidRequestsAndPriorCancellationHaveNoFilesystemEffects
File System Safety
Section titled “File System Safety”Read the assertions. Representative entry points:
WriteAllBytesReplacesTheCompletePayloadWithoutLeavingStagingFilesInstallRequiresASameDirectoryCandidateAndPreservesTheDestinationOnFailureInstallReplacesAnExistingFileWithTheCompleteCandidatePathBoundaryRejectsAbsoluteAndParentTraversalPaths
Owned Read Stream
Section titled “Owned Read Stream”Read the assertions. Representative entry points:
ReaderClosesBeforeItsIndependentOwnerAndReleaseCanBeRetried
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.