Releases: devlooped/moq
4.14.6
4.14.5
4.14.4
4.14.3
4.14.2
4.14.1
4.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)
4.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)
4.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 types
You can create your own custom type matchers:
[TypeMatcher] class Either<A, B> : ITypeMatcher { public bool Matches(Type type) => type == typeof(A) || type == typeof(B); }
-
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)
4.12.0
Changed
- Improved performance for
Mock.Of<T>
andmock.SetupAllProperties()
as the latter now performs property setups just-in-time, instead of as an ahead-of-time batch operation. (@vanashimko, #826) - Setups with no
.Returns(…)
nor.CallBase()
no longer returndefault(T)
for loose mocks, but a value that is consistent with the mock'sCallBase
andDefaultValue[Provider]
settings. (@stakx, #849)
Added
- New method overload
sequenceSetup.ReturnsAsync(Func<T>)
(@stakx, #841) - LINQ to Mocks support for strict mocks, i.e. new method overloads for
Mock.Of
,Mocks.Of
,mockRepository.Of
, andmockRepository.OneOf
that accept aMockBehavior
parameter. (@stakx, #842)
Fixed
- Adding
Callback
to a mock breaks async tests (@marcin-chwedczuk-meow, #702) mock.SetupAllProperties()
now setups write-only properties for strict mocks, so that accessing such properties will not throw anymore. (@vanashimko, #836)- Regression:
mock.SetupAllProperties()
andMock.Of<T>
fail due to inaccessible property accessors (@Mexe13, #845) - Regression:
VerifyNoOtherCalls
causes stack overflow when mock setup returns the mocked object (@bash, #846) Capture.In()
no longer captures arguments when other setup arguments do not match (@ocoanet, #844).CaptureMatch
no longer invokes the capture callback when other setup arguments do not match (@ocoanet, #844).