Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.12.0
->4.18.1
Release Notes
moq/moq4
v4.18.1
Fixed
It.Is
predicates in setup expressions after updating from 4.13.1 to 4.16.1 (@b3go, #1217)SetupProperty
where Moq fails to match a property accessor implementation against its definition in an interface (@Naxemar, #1248).Result
vs without (@cyungmann, #1253)v4.18.0
New major version of DynamicProxy (you may get better performance!), so please update with care.
Changed
Castle.Core
(DynamicProxy) from version 4.4.1 to 5.0.0 (@stakx, #1257)net45
tonet462
net6.0
TFMFixed
System.Net.Http
which is vulnerable to "DoS", "Spoofing", "Privilege Escalation", "Authentication Bypass" and "Information Exposure" (@sidseter, #1219)CallBase
andDefaultValue.Mock
configured (@IanKemp, #1249)v4.17.2
Fixed
v4.17.1
Added
SetupSet
,VerifySet
methods formock.Protected().As<>()
(@tonyhallett, #1165)Throws
method overloads that allow specifying a function with or without parameters, to provide an exception, for example.Throws(() => new InvalidOperationException())
and
Setup(x => x.GetFooAsync(It.IsAny<string>()).Result).Throws((string s) => new InvalidOperationException(s))
. (@adam-knights, #1191)Changed
Castle.Core
(DynamicProxy) from version 4.4.0 to 4.4.1 (@stakx, #1233)Fixed
_
forIt.IsAny<>()
(@adamfk, #1199)mock.Protected()
setup methods fail when argument is of typeExpression
(@tonyhallett, #1189)Protected().SetupSet()
...VerifySet
(@tonyhallett, #1186)mock.Protected().As<>()
(@tonyhallett, #1185)Verify
fail when it should not (@evilc0, #1225)Mock.Of
(@stakx, #1066)SetupAllProperties
causes mocks to become race-prone (@estrizhok, #1231)v4.16.1
Added
CallBase
can now be used with interface methods that have a default interface implementation. It will call the most specific override. (@stakx, #1130)Changed
It.Is
lambda expressions that capture local variables. (@bfriesen, #1140)Fixed
AmbiguousMatchException
raised when interface has property indexer besides property in VB. (@mujdatdinc, #1129).Result
property (@stakx, #1132)setup.Returns(InvocationFunc)
wraps thrown exceptions inTargetInvocationException
(@stakx, #1141)v4.16.0
Added
Ability to directly set up the
.Result
of tasks and value tasks, which makes setup expressions more uniform by rendering dedicated async verbs like.ReturnsAsync
,.ThrowsAsync
, etc. unnecessary:This is useful in places where there currently aren't any such async verbs at all:
This also allows recursive setups / method chaining across async calls inside a single setup expression:
or, with only
Mock.Of
:This should work in all principal setup methods (
Mock.Of
,mock.Setup…
,mock.Verify…
). Support inmock.Protected()
and for custom awaitable types may be added in the future. (@stakx, #1126)Changed
Fixed
Performance regression: Adding setups to a mock becomes slower with each setup (@CeesKaas, #1110)
Regression:
mock.Verify[All]
no longer marks invocations as verified if they were matched by conditional setups. (@Lyra2108, #1114)v4.15.2
Changed
System.Threading.Tasks.Extensions
dependency to version 4.5.4 (@JeffAshton, #1108)v4.15.1
Added
It.Is
,It.IsIn
, andIt.IsNotIn
that compare values using a customIEqualityComparer<T>
(@weitzhandler, #1064)ReturnValue
andException
onIInvocation
to query recorded invocations return values or exceptions (@MaStr11, #921, #1077)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
+=
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)Fixed
SetupProperty
fails if property getter and setter are not both defined in mocked type (@stakx, #1017)Mock.Of<>
is used in query comprehensionfrom
clause (@stakx, #982)v4.14.7
Changed
DefaultValue.Mock
now inheritSetupAllProperties
from their "parent" mock (like it says in the XML documentation) (@stakx, #1074)Fixed
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)v4.14.6
Fixed
Mock.Of
(@mariotee, #1039)v4.14.5
Fixed
VerifySet
fails withNullReferenceException
for write-only indexers (@Epicycle23, #1036)v4.14.4
Fixed
NullReferenceException
on subsequent setup if expression contains null reference (@IanYates83, #1031)v4.14.3
Fixed
Verify
behavior change usingDefaultValue.Mock
(@DesrosiersC, #1024)v4.14.2
Fixed
Verify
behavior change usingDefaultValue.Mock
(@DesrosiersC, #1024)v4.14.1
Added
SetupSequence
verbs.PassAsync()
and.ThrowsAsync(...)
for async methods withvoid
return type (@fuzzybair, #993)Fixed
StackOverflowException
onVerifyAll
when mocked method returns mocked object (@hotchkj, #1012)v4.14.0
Added
A mock's setups can now be inspected and individually verified via the new
Mock.Setups
collection andIInvocation.MatchingSetup
property (@stakx, #984-#987, #989, #995, #999)New
.Protected().Setup
andProtected().Verify
method overloads to deal with generic methods (@JmlSaul, #967)Two new public methods in
Times
:bool Validate(int count)
andstring ToString()
(@stakx, 975)Changed
Attempts to mark conditionals setup as verifiable are now considered an error, since conditional setups are ignored during verification. Calls to
.Verifiable()
on conditional setups are no-ops and can be safely removed. (@stakx, #997)When matching invocations against setups, captured variables nested inside expression trees are now evaluated. Their values likely matter more than their identities. (@stakx, #1000)
Fixed
Regression: Restored
Capture.In
use inmock.Verify(expression, ...)
to extract arguments of previously recorded invocations. (@vgriph, #968; @stakx, #974)Consistency: When mocking a class
C
whose constructor invokes one of its virtual members,Mock.Of<C>()
now operates likenew Mock<C>()
: a record of such invocations is retained in the mock'sInvocations
collection (@stakx, #980)After updating Moq from 4.10.1 to 4.11, mocking NHibernate session throws a
System.NullReferenceException
(@ronenfe, #955)v4.13.1
Fixed
SetupAllProperties
does not recognize property as read-write if only setter is overridden (@stakx, #886)Regression:
InvalidCastException
caused by Moq erroneously reusing a cached auto-mocked (DefaultValue.Mock
) return value for a different generic method instantiation (@BrunoJuchli, #932)AmbiguousMatchException when setting up the property, that hides another one (@ishatalkin, #939)
ArgumentException
("Interface not found") when setting upobject.ToString
on an interface mock (@vslynko, #942)Cannot "return" to original mocked type after downcasting with
Mock.Get
and then upcasting withmock.As<>
(@pjquirk, #943)params
arrays in recursive setup expressions are matched by reference equality instead of by structural equality (@danielcweber, #946)mock.SetupProperty
throwsNullReferenceException
when called for partially overridden property (@stakx, #951)v4.13.0
Changed
Improved error message that is supplied with
ArgumentException
thrown whenSetup
orVerify
are called on a protected method if the method could not be found with both the name and compatible argument types specified (@thomasfdm, #852).mock.Invocations.Clear()
now removes traces of previous invocations more thoroughly by additionally resetting all setups to an "unmatched" state. (@stakx, #854)Consistent
Callback
delegate validation regardless of whether or notCallback
is preceded by aReturns
: Validation for post-Returns
callback delegates used to be very relaxed, but is now equally strict as in the pre-Returns
case.) (@stakx, #876)Subscription to mocked events used to be handled less strictly than subscription to regular CLI events. As with the latter, subscribing to mocked events now also requires all handlers to have the same delegate type. (@stakx, #891)
Moq will throw when it detects that an argument matcher will never match anything due to the presence of an implicit conversion operator. (@michelcedric, #897, #898)
New algorithm for matching invoked methods against methods specified in setup/verification expressions. (@stakx, #904)
Added
Added support for setup and verification of the event handlers through
Setup[Add|Remove]
andVerify[Add|Remove|All]
(@lepijohnny, #825)Added support for lambda expressions while creating a mock through
new Mock<SomeType>(() => new SomeType("a", "b"))
andrepository.Create<SomeType>(() => new SomeType("a", "b"))
. This makes the process of mocking a class without a parameterless constructor simpler (compiler syntax checker...). (@frblondin, #884)Support for matching generic type arguments:
mock.Setup(m => m.Method<It.IsAnyType>(...))
. (@stakx, #908)The standard type matchers are:
It.IsAnyType
— matches any typeIt.IsSubtype<T>
— matchesT
and proper subtypes ofT
It.IsValueType
— matches only value typesYou can create your own custom type matchers:
In order to support type matchers (see bullet point above), some new overloads have been added to existing methods:
setup.Callback(new InvocationAction(invocation => ...))
,setup.Returns(new InvocationFunc(invocation => ...))
:The lambda specified in these new overloads will receive an
IInvocation
representing the current invocation from which type arguments as well as arguments can be discovered.Match.Create<T>((object argument, Type parameterType) => ..., ...)
,It.Is<T>((object argument, Type parameterType) => ...)
:Used to create custom matchers that work with type matchers. When a type matcher is used for
T
, theargument
received by the custom matchers is untyped (object
), and its actual type (or rather the type of the parameter for which the argument was passed) is provided via an additional parameterparameterType
. (@stakx, #908)Fixed
Moq does not mock explicit interface implementation and
protected virtual
correctly. (@oddbear, #657)Invocations.Clear()
does not causeVerify
to fail (@jchessir, #733)Regression:
SetupAllProperties
can no longer set up properties whose names start withItem
. (@mattzink, #870; @kaan-kaya, #869)Regression:
MockDefaultValueProvider
will no longer attempt to setCallBase
to true for mocks generated for delegates. (@dammejed, #874)Verify
throwsTargetInvocationException
instead ofMockException
when one of the recorded invocations was to an async method that threw. (@Cufeadir, #883)Moq does not distinguish between distinct events if they have the same name (@stakx, #893)
Regression in 4.12.0:
SetupAllProperties
removes indexer setups. (@stakx, #901)Parameter types are ignored when matching an invoked generic method against setups. (@stakx, #903)
For
[Value]Task<object>
,.ReturnsAsync(null)
throwsNullReferenceException
instead of producing a completed task with resultnull
(@voroninp, #909)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.