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.
All internal dependecies to
CoreEx
have been removed. This is intended to further generalize the capabilities ofUnitTestEx
; but more importantly, break the circular dependency reference between the two repositories. NewCoreEx.UnitTesting*
packages have been created to extend theUnitTestEx
capabilities forCoreEx
.AssertValue
for consistency; otherwise,AssertContent
for a simple string comparison.AssertJson*
for consistency.CreateServiceBusMessage
methods that accept a genericT
value have been renamed toCreateServiceBusMessageFromValue
.Expectations
capabilities have been greatly improved to support new expectations to be added/extended.GenericTester
that explicitly supports aTValue
has been added; use newGenericTester.CreateFor<TValue>
to instantiate/use.KellermanSoftware.CompareNetObjects
dependency; all comparisons use internalJsonElementComparer
which has proper/improved support for fully qualified paths, including optional array indexers. The relatedJsonElementComparerOptions
provides a means to control the comparison behaviour.ObjectComparer
has been reinstated and now leverages theJsonElementComparer
internally..NET6.0
and above; added.NET8.0
support.The enhancements have been made in a manner to maximize backwards compatibility with previous versions of
UnitTestEx
where possible; however, some breaking changes were unfortunately unavoidable (and made to improve overall). There may be an opportunity for the consuming developer to add extension methods to support the previous naming conventions if desired; note that the nextCoreEx
version (v3.6.0
) will implement extensions in newCoreEx.UnitTesting
packages to support existing behaviors (where applicable).