Releases: xmlunit/xmlunit.net
XMLUnit.NET 2.11.1
-
placeholders can now also be used inside of the local part of
xsi:typeattributes.
PR #49 -
PlaceholderDifferenceEvaluator would cause InvalidCastException for documents with
differences inxsi:typeattributes.
Equivalent of XMLUnit Java Issue #xmlunit/276 -
added readme files for the nuget packages.
Issue #46. -
the NUnit 4.x constraints package tags nunit3 rather than nunit4.
PR #43. -
added Cyclone DX SBOMs to release artifacts
Issue #47.
XMLUnit.NET 2.11.0
- introduced a new constraints library for NUnit 4.x as the NUnit 3.x
constraints can not be used with NUnit 4.x at all.
Issue #42.
XMLUnit.NET 2.10.0
-
adjusted the NUnit 3.x constraints so they should work for NUnit 4.x as well.
Issue #40. -
add a new
ElementSelectors.ByNameAndAllAttributesvariant that filters attributes before deciding whether elements can be compared.
Inspired by Issue #xmlunit/259 -
Nodes.GetMergedNestedTextandNodes.StripElementContentWhitespacehad the same problem of not knowning aboutXmlWhitespacethat caused Issue #38. And neither of the methods could deal withXmlSignificantWhitespaceat all. -
add
XmlWhitespaceStrippedSource,XmlWhitespaceNormalizedSource, andXmlElementContentWhitespaceStrippedSourcethat only trim characters that are considered whitespace by the XML Specification from textual content.
Also added new modifiers toDiffBuilderthat make use of the newISourcetypes.
Issue #39.
XMLUnit.NET 2.9.2
This is a small feature and bugfix release.
The full changelog is
-
added
NodeFilters#SatisfiesAllandSatifiesAnymethods to make it easier to combine multiple node filters.
added to simplify the use case of xmlunit/#249 -
when documents contained element content whitespace represented by
System.Xml.XmlWhitespacethe types and methods that are supposed to strip or normalize whitespace would fail.
Issue #38
XMLUnit.NET 2.9.1
XMLUnit.NET ports changes made to XMLUnit for Java 2.8.3 and 2.8.4. The full changelog is:
-
improved comparison performance for documents with many siblings
based on a suggestion by @gerpres made in Java Issue xmlunit/#236 -
added a new
FullDescriptionmethod toDiffthat provides a string-representation of all differences - not just the first one likeToStringdoes.
Based on Java PR xmlunit/#235 by @Boiarshinov
XMLUnit.NET 2.9.0
This release fixes a bug for a very specific setup and makes ISource disposable.
Full details:
-
ISourcenow extendsIDisposableto allow releasing unmanaged resources used when building sources from files or URIs.This change is backwards incompatible if you are providing
ISourceimplementations of your own.
#33. -
DefaultNodeMatcherwith multipleElementSelectors could fail to find the best matches as the order ofElementSelectors should select them.
Issue similar to xmlunit/#197
XMLUnit.NET 2.8.0
This version contains a backwards incompatible change to the IPlaceholderHandler interface that is part of the experimental placeholders module: The Evaluate method now receives a variable number of string arguments in addition to the textual content of the element/attribute. This allows placeholders like ${xmlunit.matchesRegex(some\s*regex)}.
Only the placeholder package has been changed, all other packages are functionally identical to XMLUnit.NET 2.7.2.
-
add a new
${xmlunit.isDateTime}placeholder
PRs #31 and #32 by MilkyWare -
added a new
${xmlunit.matchesRegex(regex)}placeholder
based on Java PR xmlunit/#178 by @Jazzyekim.
XMLUnit.NET 2.7.2
This release fixes a bug in the construction of XPaths in certain corner cases:
- the XPath values for comparisons resulting in
CHILD_LOOKUP
differences could be wrong whenNodeFilters were present.
Issue #29
XMLUnit.NET 2.7.1
The release fixes a bug in a corner-case and adds a new isNumber placeholder.
The full list of changes:
-
add a new
${xmlunit.isNumber}placeholder
Based on the Java PR xmlunit/#154 by @NathanAtClarity. -
the XPath values of a comparison should not be affected by any
NodeFilterbeing in effect.
Issue similar to xmlunit/#156
XMLUnit.NET 2.7.0
This release is identical to XMLUnit.NET 2.7.0-beta-01. It adds support for .NET Standard 2.0 in addition to the traditional .NET Framework 3.5.
Many thanks to @Shatl who performed most of the heavy lifting which has made this release possible.