Bump Moq from 4.14.5 to 4.15.1
Bumps Moq from 4.14.5 to 4.15.1.
Changelog
Sourced from Moq's changelog.
4.15.1 (2020-11-10)
Added
- New method overloads for
It.Is
,It.IsIn
, andIt.IsNotIn
that compare values using a customIEqualityComparer<T>
(@weitzhandler, #1064)- New properties
ReturnValue
andException
onIInvocation
to query recorded invocations return values or exceptions (@MaStr11, #921, #1077)- Support for "nested" type matchers, i.e. type matchers that appear as part of a composite type (such as
It.IsAnyType[]
orFunc<It.IsAnyType, bool>
). Argument match expressions likeIt.IsAny<Func<It.IsAnyType, bool>>()
should now work as expected, whereas they previously didn't. In this particular example, you should no longer need a workaround like(Func<It.IsAnyType, bool>)It.IsAny<object>()
as originally suggested in #918. (@stakx, #1092)Changed
- Event accessor calls (
+=
and-=
) now get consistently recorded inMock.Invocations
. This previously wasn't the case for backwards compatibility withVerifyNoOtherCalls
(which got implemented before it was possible to check them usingVerify{Add,Remove}
). You now need to explicitly verify expected calls to event accessors prior toVerifyNoOtherCalls
. Verification of+=
and-=
now works regardless of whether or not you set those up (which makes it consistent with how verification usually works). (@80O, @stakx, #1058, #1084)- Portable PDB (debugging symbols) are now embedded in the main library instead of being published as a separate NuGet symbols package (`.snupkg) (@kzu, #1098)
Fixed
SetupProperty
fails if property getter and setter are not both defined in mocked type (@stakx, #1017)- Expression tree argument not matched when it contains a captured variable – evaluate all captures to their current values when comparing two expression trees (@QTom01, #1054)
- Failure when parameterized
Mock.Of<>
is used in query comprehensionfrom
clause (@stakx, #982)4.15.0
This version was accidentally published as 4.15.1 due to an intermittent problem with NuGet publishing.
4.14.7 (2020-10-14)
Changed
- Mocks created by
DefaultValue.Mock
now inheritSetupAllProperties
from their "parent" mock (like it says in the XML documentation) (@stakx, #1074)Fixed
- Setup not triggered due to VB.NET transparently inserting superfluous type conversions into a setup expression (@InteXX, #1067)
- Nested mocks created by
Mock.Of<T>()
no longer have their properties stubbed since version 4.14.0 (@vruss, @1071)Verify
fails for recursive setups not explicitly marked asVerifiable
(@killergege, #1073)Mock.Of<>
fails for COM interop types that are annotated with a[CompilerGenerated]
custom attribute (@killergege, #1072)4.14.6 (2020-09-30)
Fixed
- Regression since 4.14.0: setting nested non-overridable properties via
Mock.Of
(@mariotee, #1039)
Commits
- See full diff in compare view