You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MoveToFolderAsync_WhenArchiveRootResolves_StillReadsItOnce terminates its success path on a NullReferenceException raised by the EmailFiler collaborator rather than on a deliberate stopping
point. The test is correct today, but its failure message would misdirect a future maintainer if EmailFiler.SortAsync ever gains a null guard.
Environment
OS/version: Windows 11, .NET Framework 4.8.1
Python version: not applicable; this is an MSTest C# unit test
The test terminates the success path deliberately and asserts only the invariant it exists to pin,
which is olObjects.VerifyGet(value => value.ArchiveRootPath, Times.Once()). A failure reports a
problem with the archive-root read count.
Actual Behavior
The test asserts await act.Should().ThrowAsync<NullReferenceException>() before the VerifyGet. That
exception is not a property of the unit under test: it is the EmailFiler collaborator dereferencing
a MailItemHelper whose folder information is null, several frames past the code issue 638 touched.
Once EmailFiler no longer throws there, the test fails with a message about a missing NullReferenceException and points at the wrong subsystem.
Logs / Screenshots
Attached minimal logs or screenshot
Snippet: not captured; the condition is latent and does not reproduce against the current tree.
Superseded by consolidated issue #736, which tracks this finding along with related ones sharing the same blast radius (EFC ArchiveRootPath / BoundaryErrorSink defects). See #736 for detail.
Activity
drmoisan commentedon Sep 2, 2026
Superseded by consolidated issue #736, which tracks this finding along with related ones sharing the same blast radius (EFC ArchiveRootPath / BoundaryErrorSink defects). See #736 for detail.
docs(potential): consolidate 11 issues into 3 blast-radius clusters