Sun, 08. Mar 2020
Both releases fix a common bug where the XPath reported for missing nodes could be wrong in certain edge cases.
- the XPath values for comparisons resulting in
CHILD_LOOKUP
differences could be wrong whenNodeFilter
s were present. XMLUnit.NET Issue #29
This is the only change in XMLUnit.NET. In XMLUnit for Java the AssertJ module has also been improved and is supposed to be compatible with AssertJ 3.13+ now.
The full list of changes for XMLUnit for Java:
- the dependencies on JAXB implementation and its transitive dependencies has been promoted from test scope to optional for Java 9 and later Issue #162
- added
containsAnyNodeHavingXPath
,containsAllNodesHavingXPath
andhasXPath
assertions to xmlunit-assertj. - added
extractingAttribute
method to xmlunit-assertj. - removed some redundant
instanceof
checks. PR #171 by @PascalSchumacher. - xmlunit-assertj should now work with AssertJ-Core 3.13.x Issue #166
- xmlunit-legacy will now use
NewDifferenceEngine
even when anElementQualifier
different from the built-in ones is used.
path: /en/oss/XMLUnit | #