Bump the test-tooling group with 7 updates - #3
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps Microsoft.NET.Test.Sdk to 17.3.3 Bumps Moq from 4.7.99 to 4.20.72 Bumps NUnit from 3.13.3 to 4.6.1 Bumps NUnit3TestAdapter from 4.2.1 to 6.2.0 Bumps Verify.Xunit from 17.1.1 to 20.8.2 Bumps xunit from 2.4.1 to 2.9.3 Bumps Xunit.SkippableFact from 1.4.13 to 1.5.61 --- updated-dependencies: - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 17.3.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: test-tooling - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 17.3.3 dependency-type: direct:production update-type: version-update:semver-major dependency-group: test-tooling - dependency-name: Moq dependency-version: 4.20.72 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: test-tooling - dependency-name: NUnit dependency-version: 4.6.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: test-tooling - dependency-name: NUnit3TestAdapter dependency-version: 6.2.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: test-tooling - dependency-name: Verify.Xunit dependency-version: 20.8.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: test-tooling - dependency-name: xunit dependency-version: 2.9.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: test-tooling - dependency-name: Xunit.SkippableFact dependency-version: 1.5.61 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: test-tooling ... Signed-off-by: dependabot[bot] <support@github.com>
Author
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/tests/RazorLight.Precompile.Tests/test-tooling-7d4e82bce1
branch
August 7, 2026 00:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated Microsoft.NET.Test.Sdk from 16.5.0 to 17.3.3.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
17.3.3
See the release notes here.
17.3.2
See the release notes here.
17.3.1
See the release notes here.
17.3.0
See the release notes here.
17.3.0-preview-20220612-01
See the release notes here.
17.3.0-preview-20220530-08
See the release notes here.
17.3.0-preview-20220426-02
See the release notes here.
17.2.1
See the release notes here.
17.2.0
See the release notes here.
17.2.0-preview-20220401-08
See the release notes here.
17.2.0-preview-20220401-07
See the release notes here.
17.2.0-preview-20220301-01
See the release notes here.
17.2.0-preview-20220131-20
See the release notes here.
17.1.0
See the release notes here.
17.1.0-release-20220113-05
See the release notes here.
17.1.0-preview-20211130-02
See the release notes here.
17.1.0-preview-20211109-03
See the release notes here.
17.0.2
See the release notes here.
17.0.0
See the release notes here.
16.11.0
See the release notes here.
16.10.0
See the release notes here.
16.10.0-release-20210429-01
See the release notes here.
16.10.0-release-20210422-02
See the release notes here.
16.10.0-release-20210330-02
See the release notes here.
16.10.0-release-20210329-03
See the release notes here.
16.10.0-preview-20210219-03
See the release notes here.
16.9.4
See the release notes here.
16.9.1
See the release notes here.
16.9.0-preview-20210127-04
See the release notes here.
16.9.0-preview-20210106-01
See the release notes here.
16.9.0-preview-20201123-03
See the release notes here.
16.9.0-preview-20201020-06
See the release notes here.
16.9.0-preview-20201020-06
Issue Fixed
Microsoft.TestPlatform.TestHostNuGet #2569See full log here
Drops
16.8.3
See the release notes here.
16.8.0
See the release notes here.
16.8.0-preview-20200921-01
See the release notes here.
16.8.0-preview-20200812-03
See the release notes here.
16.8.0-preview-20200806-02
See the release notes here.
16.7.1
See the release notes here
16.7.0
See the release notes here.
16.7.0-preview-20200519-01
See the release notes here.
16.7.0-preview-20200428-01
See the release notes here.
16.6.1
See the release notes here.
16.6.0
See the release notes here.
16.6.0-preview-20200318-01
See the release notes here.
16.6.0-preview-20200310-03
See the release notes here.
16.6.0-preview-20200309-01
See the release notes here.
16.6.0-preview-20200226-03
See the release notes here.
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 17.0.0 to 17.3.3.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
17.3.3
See the release notes here.
17.3.2
See the release notes here.
17.3.1
See the release notes here.
17.3.0
See the release notes here.
17.3.0-preview-20220612-01
See the release notes here.
17.3.0-preview-20220530-08
See the release notes here.
17.3.0-preview-20220426-02
See the release notes here.
17.2.1
See the release notes here.
17.2.0
See the release notes here.
17.2.0-preview-20220401-08
See the release notes here.
17.2.0-preview-20220401-07
See the release notes here.
17.2.0-preview-20220301-01
See the release notes here.
17.2.0-preview-20220131-20
See the release notes here.
17.1.0
See the release notes here.
17.1.0-release-20220113-05
See the release notes here.
17.1.0-preview-20211130-02
See the release notes here.
17.1.0-preview-20211109-03
See the release notes here.
17.0.2
See the release notes here.
Commits viewable in compare view.
Updated Moq from 4.7.99 to 4.20.72.
Release notes
Sourced from Moq's releases.
4.20.72
What's Changed
🔨 Other
Full Changelog: devlooped/moq@v4.20.71...v4.20.72
4.20.71
What's Changed
🔨 Other
New Contributors
Full Changelog: devlooped/moq@v4.20.70...v4.20.71
4.20.70
What's Changed
🔨 Other
New Contributors
Full Changelog: devlooped/moq@v4.20.69...v4.20.70
4.20.69
Let's make it more memorable when Moq became "safe" again.
What's Changed
4.20.2
What's Changed
🐛 Fixed bugs
Full Changelog: moq/moq.spikes@v4.20.1...v4.20.2
4.20.1
What's Changed
✨ Implemented enhancements
Full Changelog: moq/moq.spikes@v4.20.0...v4.20.1
4.20.0
What's Changed
✨ Implemented enhancements
setup.Verifiable(Times times, [string failMessage])method by @stakx in https://github.com/moq/moq/pull/1319🔨 Other
Mock<T>.RaiseAsyncby @stakx in https://github.com/moq/moq/pull/1313ThrowsAsyncfor non-genericValueTaskby @johnthcall in https://github.com/moq/moq/pull/1235mock.Protected().Verify<T>()method overload by @stakx in https://github.com/moq/moq/pull/1325New Contributors
Full Changelog: moq/moq.spikes@v4.18.4...v4.20.0
4.20.0-rc
What's Changed
🔨 Other
Full Changelog: moq/moq.spikes@v4.20.0-beta...v4.20.0-rc
4.20.0-beta
What's Changed
✨ Implemented enhancements
setup.Verifiable(Times times, [string failMessage])method by @stakx in https://github.com/moq/moq/pull/1319🔨 Other
Mock<T>.RaiseAsyncby @stakx in https://github.com/moq/moq/pull/1313ThrowsAsyncfor non-genericValueTaskby @johnthcall in https://github.com/moq/moq/pull/1235mock.Protected().Verify<T>()method overload by @stakx in https://github.com/moq/moq/pull/1325New Contributors
Full Changelog: moq/moq.spikes@v4.18.4...v4.20.0-beta
4.20.0-alpha
What's Changed
✨ Implemented enhancements
setup.Verifiable(Times times, [string failMessage])method by @stakx in https://github.com/moq/moq/pull/1319🔨 Other
Mock<T>.RaiseAsyncby @stakx in https://github.com/moq/moq/pull/1313ThrowsAsyncfor non-genericValueTaskby @johnthcall in https://github.com/moq/moq/pull/1235mock.Protected().Verify<T>()method overload by @stakx in https://github.com/moq/moq/pull/1325New Contributors
Full Changelog: moq/moq.spikes@v4.18.4...v4.20.0-alpha
4.18.4
Changed
Castle.Core(DynamicProxy) from version 5.1.0 to 5.1.1 (@stakx, #1317)4.18.3
Fixed
SetupAllPropertiescrashes when invoked on aMock<T>subclass (@mo-russo, #1278)4.18.2
Changed
Castle.Core(DynamicProxy) from version 5.0.0 to 5.1.0 (@stakx, #1275)System.Threading.Tasks.Extensionsfornetstandard2.1andnet6.0(@tibel, #1274)Fixed
.Raises()with redeclared event (@howcheng, #1175)MissingMethodExceptionwhen mocking interface with sealed default implementation (@pjquirk, #1209)TypeLoadExceptionon mock when a record has a base record on .NET 6 (@tgrieger-sf, #1273)4.18.1
Fixed
It.Ispredicates in setup expressions after updating from 4.13.1 to 4.16.1 (@b3go, #1217)SetupPropertywhere Moq fails to match a property accessor implementation against its definition in an interface (@Naxemar, #1248).Resultvs without (@cyungmann, #1253)4.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)net45tonet462net6.0TFMFixed
System.Net.Httpwhich is vulnerable to "DoS", "Spoofing", "Privilege Escalation", "Authentication Bypass" and "Information Exposure" (@sidseter, #1219)CallBaseandDefaultValue.Mockconfigured (@IanKemp, #1249)4.17.2
Fixed
4.17.1
Added
SetupSet,VerifySetmethods formock.Protected().As<>()(@tonyhallett, #1165)Throwsmethod 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)Verifyfail when it should not (@evilc0, #1225)Mock.Of(@stakx, #1066)SetupAllPropertiescauses mocks to become race-prone (@estrizhok, #1231)4.16.1
Added
CallBasecan now be used with interface methods that have a default interface implementation. It will call the most specific override. (@stakx, #1130)Changed
It.Islambda expressions that capture local variables. (@bfriesen, #1140)Fixed
AmbiguousMatchExceptionraised when interface has property indexer besides property in VB. (@mujdatdinc, #1129).Resultproperty (@stakx, #1132)setup.Returns(InvocationFunc)wraps thrown exceptions inTargetInvocationException(@stakx, #1141)4.16.0
Added
Ability to directly set up the
.Resultof 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)4.15.2
Changed
System.Threading.Tasks.Extensionsdependency to version 4.5.4 (@JeffAshton, #1108)4.15.1
Added
It.Is,It.IsIn, andIt.IsNotInthat compare values using a customIEqualityComparer<T>(@weitzhandler, #1064)ReturnValueandExceptiononIInvocationto 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
SetupPropertyfails if property getter and setter are not both defined in mocked type (@stakx, #1017)Mock.Of<>is used in query comprehensionfromclause (@stakx, #982)4.14.7
Changed
DefaultValue.Mocknow inheritSetupAllPropertiesfrom 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)Verifyfails 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
Fixed
Mock.Of(@mariotee, #1039)4.14.5
Fixed
VerifySetfails withNullReferenceExceptionfor write-only indexers (@Epicycle23, #1036)4.14.4
Fixed
NullReferenceExceptionon subsequent setup if expression contains null reference (@IanYates83, #1031)4.14.3
Fixed
Verifybehavior change usingDefaultValue.Mock(@DesrosiersC, #1024)4.14.2
Fixed
Verifybehavior change usingDefaultValue.Mock(@DesrosiersC, #1024)4.14.1
Added
SetupSequenceverbs.PassAsync()and.ThrowsAsync(...)for async methods withvoidreturn type (@fuzzybair, #993)Fixed
StackOverflowExceptiononVerifyAllwhen mocked method returns mocked object (@hotchkj, #1012)4.14.0
Added
A mock's setups can now be inspected and individually verified via the new
Mock.Setupscollection andIInvocation.MatchingSetupproperty (@stakx, #984-#987, #989, #995, #999)New
.Protected().SetupandProtected().Verifymethod 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.Inuse inmock.Verify(expression, ...)to extract arguments of previously recorded invocations. (@vgriph, #968; @stakx, #974)Consistency: When mocking a class
Cwhose 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'sInvocationscollection (@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
SetupAllPropertiesdoes not recognize property as read-write if only setter is overridden (@stakx, #886)Regression:
InvalidCastExceptioncaused 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.ToStringon an interface mock (@vslynko, #942)Cannot "return" to original mocked type after downcasting with
Mock.Getand then upcasting withmock.As<>(@pjquirk, #943)paramsarrays in recursive setup expressions are matched by reference equality instead of by structural equality (@danielcweber, #946)mock.SetupPropertythrowsNullReferenceExceptionwhen called for partially overridden property (@stakx, #951)4.13.0
Changed
Improved error message that is supplied with
ArgumentExceptionthrown whenSetuporVerifyare 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
Callbackdelegate validation regardless of whether or notCallbackis preceded by aReturns: Validation for post-Returnscallback delegates used to be very relaxed, but is now equally strict as in the pre-Returnscase.) (@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>— matchesTand proper subtypes ofTIt.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
IInvocationrepresenting 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, theargumentreceived 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)... (truncated)
4.12.0
Changed
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).Returns(…)nor.CallBase()no longer returndefault(T)for loose mocks, but a value that is consistent with the mock'sCallBaseandDefaultValue[Provider]settings. (@stakx, #849)Added
sequenceSetup.ReturnsAsync(Func<T>)(@stakx, #841)Mock.Of,Mocks.Of,mockRepository.Of, andmockRepository.OneOfthat accept aMockBehaviorparameter. (@stakx, #842)Fixed
Callbackto 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)mock.SetupAllProperties()andMock.Of<T>fail due to inaccessible property accessors (@Mexe13, #845)VerifyNoOtherCallscauses 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).CaptureMatchno longer invokes the capture callback when other setup arguments do not match (@ocoanet, #844).4.11.0
Same as 4.11.0 Release Candidate 2. See changelog entries for the two pre-release versions.
4.11.0-rc2
This is a pre-release version.
Changed
Moq.pdb) have moved into a separate NuGet symbol package (as per the current official guideline). If you want the Visual Studio debugger to step into Moq's source code, disable Just My Code, enable SourceLink, and configure NuGet's symbol server. (@stakx, #789)Fixed
SetupProperty(@stakx, #823)4.11.0-rc1
This is a pre-release version.
It contains several minor breaking changes, and there have been extensive internal rewrites in order to fix some very long-standing bugs in relation to argument matchers in fluent setup expressions.
Changed
The library now targets .NET Standard 2.0 instead of .NET Standard 1.x. This has been decided based on the official cross-platform targeting guideline and the End of Life announcement for .NET Core 1.x (@stakx, #784, #785)
Method overload resolution may change for:
mock.Protected().Setup("VoidMethod", ...)mock.Protected().Verify("VoidMethod", ...)mock.Protected().Verify<TResult>("NonVoidMethod", ...)due to a new overload: If the first argument is a
bool, make sure that argument gets interpreted as part ofargs, not asexactParameterMatch(see also Added section below). (@stakx & @Shereef, #751, #753)mock.Verify[All]now performs a more thorough error aggregation. Error messages of inner/recursive mocks are included in the error message using indentation to show the relationship between mocks. (@stakx, #762)mock.Verifyno longer creates setups, nor will it override existing setups, as a side-effect of using a recursive expression. (@stakx, #765)More accurate detection of argument matchers with
SetupSetandVerifySet, especially when used in fluent setup expressions or with indexers (@stakx, #767)mock.Verify(expression)error messages now contain a full listing of all invocations that occurred across all involved mocks. Setups are no longer listed, since they are completely irrelevant in the context of call verification. (@stakx, #779, #780)Indexers used as arguments in setup expressions are now eagerly evaluated, like all other properties already are (except when they refer to matchers) (@stakx, #794)
Update package reference to
Castle.Core(DynamicProxy) from version 4.3.1 to 4.4.0 (@stakx, #797)Added
New method overloads:
mock.Protected().Setup("VoidMethod", exactParameterMatch, args)mock.Protected().Verify("VoidMethod", times, exactParameterMatch, args)mock.Protected().Verify<TResult>("NonVoidMethod", times, exactParameterMatch, args)having a
bool exactParameterMatchparameter. Due to method overload resolution, it was easy to think this already existed when in fact it did not, leading to failing tests. (@Shereef & @stakx, #753, #751)Ability in
mock.Raiseandsetup.Raisesto raise events on sub-objects (inner mocks) (@stakx, #772)Removed
Fixed
InvalidOperationExceptionwhen specifiying setup on mock with mock containing property of typeNullable<T>(@dav1dev, #725)Verifygets confused between the same generic and non-generic signature (@lepijohnny, #749)Verifydespite being "unreachable" (@stakx, #703)Verifycan create setups that cause subsequentVerifyAllto fail (@stakx & @lepijohnny, #699)mock.Raisethrows (@MutatedTomato, #738)Mock.Raiseonly raises events on root object (@hallipr, #166)It.IsAny()as the value, even if given in the indexer argument (@idigra, #696)VerifySetfails on non-trivial property setup (@TimothyHayes, #430)SetupSet'forgets' method setup (@TimothyHayes, #432)Verify[All]fails because of lazy (instead of eager) setup argument expression evaluation (@aeslinger, #711)... (truncated)
4.10.1
Fixed
NullReferenceExceptionwhen usingSetupSeton indexers with multiple parameters (@idigra, #694)CallBaseshould not be allowed for delegate mocks (@tehmantra, #706)Changed
System.ValueTupleNuGet package, at no functional cost (i.e. value tuples are still supported just fine) (@stakx, #721)System.Reflection.TypeExtensionsandSystem.Threading.Tasks.Extensionsdependencies to versions 4.5.1 (@stakx, #729)4.10.0
Added
ExpressionCompiler: An extensibility point for setting up alternate LINQ expression tree compilation strategies (@stakx, #647)setup.CallBase()forvoidmethods (@stakx, #664)VerifyNoOtherCallsforMockRepository(@BlythMeister, #682)Changed
VerifyNoOtherCallstake into account previous calls to parameterlessVerify()andVerifyAll()(@stakx, #659)VerifyAllnow succeeds after a call toSetupAllPropertieseven when not all property accessors were invoked (stakx, #684)Fixed
outparameter detection for mocking COM interfaces with[in,out]parameters (@koutinho, #645)Returnscallback methods that have been compiled fromExpressions (@stakx, #654)Verifyexception should report configured setups for delegate mocks (@stakx, #679)Verifyexception should include complete call expression for delegate mocks (@stakx, #680)VerifyAllfail" (@stakx, #684)VerifyAllbehavior" (@stakx, #684)4.9.0
Added
Mock.Invocationsproperty to support inspection of invocations on a mock (@Tragedian, #560)Changed
Castle.Core(DynamicProxy) from version 4.3.0 to 4.3.1 (@stakx, #635)Fixed
CallBasedisregarded for some base methods from non-public interfaces (@stakx, #641)Obsoleted
mock.ResetCalls()has been deprecated in favor ofmock.Invocations.Clear()(@stakx, #633)4.8.3
Added
ISetupSequentialResult<TResult>.Returnsmethod overload that support delegate for deferred results (@snrnats, #594)inparameter modifier (@stakx, #624, #625)ReturnsAsyncandThrowsAsyncfor sequential setups of methods returning aValueTask(@stakx, #626)Changed
ReturnsAsyncandThrowsAsyncsetup methods now consistently return a newTaskon each invocation (@snrnats, #595)Mock.Of<T>()by approx. one order of magnitude (@informatorius, #598)Castle.Core(DynamicProxy) from version 4.2.1 to 4.3.0 (@stakx, #624)Fixed
ReturnsExtensions.ThrowsAsync()can causeUnobservedTaskException(@snrnats, #595)ReturnsAsyncandThrowsAsyncwith delay parameter starts timer at setup (@snrnats, #595)Returnsregression with null function callback (@Caraul, #602)4.8.2
Changed
System.ValueTupledependency to version 4.4.0 in order to reestablish Moq compatibility with .NET 4.7 (and later), which already include theValueTupletypes (@stakx, #591)Fixed
CallbackandReturns(@Caraul, #575)CallBaseregression with members of additional interfaces (@stakx, #583)4.8.1
Added
DefaultValue.EmptyandDefaultValue.Mock(@stakx, #563)Changed
System.Threading.Tasks.ExtensionsandSystem.ValueTupledependencies to versions 4.3.0 as suggested by @tothdavid in order to improve Moq compatibility with .NET 4.6.1 / help preventMissingMethodExceptionand similar (@stakx, #571)Fixed
CallBaseregression with explicitly implemented interface methods (@stakx, #558)4.8.0
Same as 4.8.0 Release Candidate 1, plus some significant speed improvements.
Changed
SetupAllPropertiesnow fully supports property type recursion / loops in the object graph, thanks to deferred property initialization (@stakx, #550)4.8.0-rc1
This is a pre-release version.
Added
voidmethods (@alexbestul, #463)SetupSequence) of protected members (@stakx, #493)reforoutparameters via two new overloads ofCallbackandReturns(@stakx, #468)mock.Protected().As<TAnalog>()interface (@stakx, #495, #501)ValueTask<TResult>when using theReturnsAsyncextension methods, similar toTask<TResult>(@AdamDotNet, #506)ValueTask<TResult>withDefaultValue.Empty(@stakx, #529)DefaultValue.EmptyandDefaultValue.Mock:Implement custom providers by subclassing either
DefaultValueProviderorLookupOrFallbackDefaultValueProvider,install them by setting
Mock[Repository].DefaultValueProvider(@stakx, #533, #536)DefaultValue.Mockto mockTask<TMockable>andValueTask<TMockable>(@stakx, #502)refparameters withIt.Ref<T>.IsAny(orItExpr.Ref<T>.IsAnyfor protected methods) as you would withIt.IsAny<T>()for regular parameters (@stakx, #537)Mock.VerifyNoOtherCalls()to check whether all expected invocations have been verified -- can be used as an alternative toMockBehavior.Strict(@stakx, #539)Changed
SetupSequencenow overrides pre-existing setups like all otherSetupmethods do. This means that exhausted sequences no longer fall back to previous setups to produce a "default" action or return value. (@stakx, #476)Returnsare validated a little more strictly than before (return type and parameter count must match with method being set up) (@stakx, #520)major.minor.0.0to help prevent assembly version conflicts and to reduce the need for binding redirects (@stakx, #554)Fixed
SetupSequenceare now thread-safe (@stakx, #476)add_X,remove_X) so they can be verified (@stakx, #488)Setupthrows when an attempt is made to set one up (@stakx, #497)SetupAllPropertiesskip inaccessible methods (@stakx, #499)IEnumerable<T>(@stakx, #510)MockVerificationExceptiontype; remove it (@stakx, #511)Mock.Ofsetup expression (@stakx, #528)Obsoleted
[Matcher]has been deprecated in favor ofMatch.Create(@stakx, #514)Commits viewable in compare view.
Updated NUnit from 3.13.3 to 4.6.1.
Release notes
Sourced from NUnit's releases.
4.6.1
See release notes for details.
4.6.0
See release notes for details.
4.5.1
See release notes for details.
4.5.0
See release notes for details.
4.4.0
See release notes for details.
4.3.2
This is a hotfix release.
See release notes for details.
4.3.1
This is a hotfix release.
See release notes for details.
4.3.0
See release notes
4.2.2
Hotfix for fixing regression bug #4802
What's Changed
Full Changelog: nunit/nunit@4.2.1...4.2.2
4.2.1
Hotfix release for Issue #4794 and #4795, affecting .Net Framework.
4.2.0
See release notes
4.1.0
See release notes
4.0.1
Patch release to fix windows targets
See release notes
and
See migration guide
4.0.0
See release notes
and
See migration guide
4.0.0-beta.1
See release notes
and information
3.14.0
See release notes
Commits viewable in compare view.
Updated NUnit3TestAdapter from 4.2.1 to 6.2.0.
Release notes
Sourced from NUnit3TestAdapter's releases.
6.2.0
See release notes
6.1.0
See release notes
6.0.1
See release notes
6.0.0
See release notes
5.2.0
See release notes
5.1.0
See release notes
5.0.0
See release notes
4.6.0
See release notes
4.5.0
Release for support of NUnit4
Fix for Issue #1100
4.4.2
Hotfix release for the issues nunit/nunit3-vs-adapter#1065, nunit/nunit3-vs-adapter#1066, nunit/nunit3-vs-adapter#1069 and nunit/nunit3-vs-adapter#1070
What's Changed
Full Changelog: nunit/nunit3-vs-adapter@V4.4.0...V4.4.2
4.4.1
Hotfix release for the issues #1065, #1066, #1069 and #1070
4.4.0
See release notes here
4.4.0-beta.1
See release notes here
4.3.2
A hotfix release for adapter version 4.3 for Issue #1144
Ability to run under .net 8, while targeting net framework 4.5
4.3.1
See release notes here
4.3.0
See release notes here
Commits viewable in compare view.
Updated Verify.Xunit from 17.1.1 to 20.8.2.
Release notes
Sourced from Verify.Xunit's releases.
20.8.1
As part of this release we had 6 commits which resulted in 1 issue being closed.
Bug
20.8.0
As part of this release we had 9 commits which resulted in 1 issue being closed.
Feature
20.7.0
As part of this release we had 20 commits which resulted in 1 issue being closed.
Feature
20.6.0
As part of this release we had 16 commits which resulted in 1 issue being closed.
Feature
20.5.0
As part of this release we had 1 issue closed.
Improvement
20.4.0
As part of this release we had 26 commits which resulted in 2 issues being closed.
Bug
Feature
20.3.2
As part of this release we had 1 issue closed.
Feature
20.3.0
As part of this release we had 1 commit which resulted in 1 issue being closed.
Feature
20.2.0
As part of this release we had 10 commits which resulted in 1 issue being closed.
Feature
20.1.1
As part of this release we had 6 commits which resulted in 1 issue being closed.
Bug
20.1.0
As part of this release we had 23 commits which resulted in 4 issues being closed.
Bug
Features
20.0.0
As part of this release we had 35 commits which resulted in 1 issue being closed.
Feature
19.14.1
As part of this release we had 9 commits which resulted in 1 issue being closed.
Bug
19.14.0
As part of this release we had 7 commits which resulted in 1 issue being closed.
Feature
19.13.1
As part of this release we had 1 issue closed.
Bug
19.12.2
As part of this release we had 12 commits which resulted in 1 issue being closed.
Feature
19.12.1
As part of this release we had 6 commits which resulted in 1 issue being closed.
Feature
19.12.0
As part of this release we had 19 commits which resulted in 1 issue being closed.
Feature
19.11.2
As part of this release we had 1 issue closed.
Feature
19.11.0
As part of this release we had 45 commits which resulted in 3 issues being closed.
Features
19.10.0
As part of this release we had 5 issues closed.
Bugs
Features
19.9.0
As part of this release we had 8 commits which resulted in 1 issue being closed.
Feature
19.8.3
As part of this release we had 7 commits which resulted in 1 issue being closed.
Bug
19.8.2
As part of this release we had 4 commits which resulted in 2 issues being closed.
Bugs
19.8.1
As part of this release we had 6 commits which resulted in 1 issue being closed.
Bug
19.8.0
As part of this release we had 11 commits which resulted in 1 issue being closed.
Feature
19.7.1
As part of this release we had 9 commits which resulted in 1 issue being closed.
Feature
19.7.0
As part of this release we had 70 commits which resulted in 2 issues being closed.
Features
_Descrip...
Description has been truncated