Activity for XML Unit

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Fri, 24 Oct 2025 12:46:51 -0000

This release is identical to XMLUnit for Java 2.10.4 except for the dependency list of the xmlunit-jakarta-jaxb-impl modulle. If you don't use the module, you can ignore this release. Up until XMLUnit 2.10.4 the xmlunit-jakarta-jaxb-impl module depended on org.glassfish.jaxb:jaxb-runtime making it more difficult to chose a different JAXB implementation than necessary (see #313). This dependency has now been removed. If you use the xmlunit-jakarta-jaxb-impl module you may now need to specify the JAXB...

Stefan Bodewig created a blog post

Stefan Bodewig — Fri, 24 Oct 2025 12:46:22 -0000

XMLUnit for Java 2.11.0 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Sat, 13 Sep 2025 13:29:23 -0000

This is a bugfix release. Fixed bugs: attributes with null values could cause a NullPointerException. Issue #307 PR #309

Stefan Bodewig created a blog post

Stefan Bodewig — Sat, 13 Sep 2025 13:28:42 -0000

XMLUnit for Java 2.10.4 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Thu, 19 Jun 2025 14:25:17 -0000

This release fixes OSGi headers inside xmlunit-core's and xmlunit-legacy's manifests, it doesn't contain any other changes. Full list of changes: marked OSGi Import-Package optional for javax.xml.bind packages in xmlunit-core. Also fixed the Export-Package header of the legacy module. Issue #300 PR #301

Stefan Bodewig created a blog post

Stefan Bodewig — Thu, 19 Jun 2025 14:24:39 -0000

XMLUnit for Java 2.10.3 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Fri, 23 May 2025 10:23:20 -0000

This release fixes a problem with the published POM of the xmlunit-legacy module. It doesn't contain any changes to any of the other modules.

Stefan Bodewig created a blog post

Stefan Bodewig — Fri, 23 May 2025 10:22:51 -0000

XMLUnit for Java 2.10.2 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Mon, 19 May 2025 03:54:46 -0000

Both releases come with build related changes but also fix some issues with the placeholders module. List of changes for XMLUnit for Java placeholders can now also be used inside of the local part of xsi:type attributes. PR #293 PlaceholderDifferenceEvaluator would cause ClassCastException for documents with differences in xsi:type attributes. Issue #276 updated a bunch of Maven plugins, in particular we now create CylcloneDX files using version 1.6 of the schema. PR #292 updated bytebuddy dependency...

Stefan Bodewig created a blog post

Stefan Bodewig — Mon, 19 May 2025 03:54:36 -0000

XMLUnit for Java 2.10.1 and XMLUnit.NET 2.11.1 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Sat, 29 Mar 2025 06:39:03 -0000

Back when I releasedXMLUnit.NET 2.10.0 I claimed the NUnit 3.x constraints would nowsupport NUnit 4.x as well. Unfortunately I never really tested this and it turns out to be wrong. NUnit 4.x is a major release and it has broken backwards compatibility (it is a major version, after all) in a way that doesn't seem to allow using the same constraint implementation for 3.x and 4.x. XMLUnit 2.11.0 adds a new XMLUnit.NUnit4.Constraints package with constraints for NUnit 4.x. This package requires at least...

Stefan Bodewig created a blog post

Stefan Bodewig — Sat, 29 Mar 2025 06:38:27 -0000

XMLUnit.NET 2.11.0 released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Thu, 08 Aug 2024 19:26:41 -0000

adjusted the NUnit 3.x constraints so they should work for NUnit 4.x as well. Issue #40. add a new ElementSelectors.ByNameAndAllAttributes variant that filters attributes before deciding whether elements can be compared. Inspired by Issue #xmlunit/259 Nodes.GetMergedNestedText and Nodes.StripElementContentWhitespace had the same problem of not knowning about XmlWhitespace that caused Issue #38. And neither of the methods could deal with XmlSignificantWhitespace at all. add XmlWhitespaceStrippedSource,...

Stefan Bodewig created a blog post

Stefan Bodewig — Thu, 08 Aug 2024 19:25:36 -0000

XMLUnit.NET 2.10.0 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Sun, 28 Apr 2024 15:18:51 -0000

add a new ElementSelectors.byNameAndAllAttributes variant that filters attributes before deciding whether elements can be compared. Inspired by Issue #259 By default the TransformerFactorys created will now try to disable extension functions. If you need extension functions for your transformations you may want to pass in your own instance of TransformerFactory and TransformerFactoryConfigurer may help with that. Inspired by Issue #264 JAXPXPathEngine will now try to disable the execution of extension...

Stefan Bodewig created a blog post

Stefan Bodewig — Sun, 28 Apr 2024 15:18:20 -0000

XMLUnit for Java 2.10.0 Released

Richard Zhu posted a comment on discussion Open Discussion

Richard Zhu — Tue, 04 Jul 2023 17:49:41 -0000

Since I can't get the XPath from XmlAttribute or XmlNode parameter passed into the predicate, how can I determine the XPath of the element to filter? Shouldn't the XPath be passed in as a parameter? Thanks.

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Thu, 16 Mar 2023 16:12:15 -0000

added NodeFilters#SatisfiesAll and SatifiesAny methods 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.XmlWhitespace the types and methods that are supposed to strip or normalize whitespace would fail. Issue #38

Stefan Bodewig created a blog post

Stefan Bodewig — Thu, 16 Mar 2023 16:11:32 -0000

XMLUnit.NET 2.9.2 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Tue, 10 Jan 2023 15:42:10 -0000

fixed some AssertJ tests that didn't work on Windows. Issue #252 and PR #253 by @Boiarshinov added overloads to ElementSelectors.byXPath that accept a XPathEngine argument. Issue #255 added Cyclone DX SBOMs to release artifacts

Stefan Bodewig created a blog post

Stefan Bodewig — Tue, 10 Jan 2023 15:41:26 -0000

XMLUnit for Java 2.9.1 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Tue, 25 Jan 2022 17:38:35 -0000

The major change of XMLUnit for Java 2.9.0 is the addition of a new module xmlunit-jakarta-jaxb-impl that can be used in addition to xmlunit-core when you want to use the Jakarta XML Binding API in version 3. For details please see the user's guide. The full list of changes of XMLUnit for Java 2.9.0 is: added a new module xmlunit-jakarta-jaxb-impl that makes Input.fromJaxb use jakarta.xml.bind rather than javax.xml.bind. For more details see the User's Guide. This change is not fully backwards compatible....

Stefan Bodewig created a blog post

Stefan Bodewig — Tue, 25 Jan 2022 17:37:58 -0000

XMLUnit for Java 2.9.0

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Thu, 16 Dec 2021 20:47:41 -0000

I've just released new minor versions of XMLUnit for Java and XMLUnit.NET. Both releases are improvements. Changelog for XMLUnit for Java 2.8.4: improved comparison performance for documents with many siblings based on a suggestion by @gerpres made in #236 Changelog for XMLUnit.NET 2.9.1 improved comparison performance for documents with many siblings based on a suggestion by @gerpres made in Java Issue xmlunit/#236 added a new FullDescription method to Diff that provides a string-representation...

Stefan Bodewig created a blog post

Stefan Bodewig — Thu, 16 Dec 2021 20:46:43 -0000

XMLUnit for Java 2.8.4 and XMLUnit.NET 2.9.1 Released

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Sun, 17 Oct 2021 19:46:15 -0000

This release fixes a shortcoming of the AssertJ support modules and adds a new convenience feature to the Diff class. The full list of changes: added a new fullDescription method to Diff that provides a string-representation of all differences - not just the first one like toString does. PR #235 fixing #232 by @Boiarshinov made sure AssertJ's methods to override the assertion message like withFailMessage are honored. #225 adjusted unit tests so they pass when AssertJ 3.19.0 is used. PR #212 by m...

Stefan Bodewig created a blog post

Stefan Bodewig — Sun, 17 Oct 2021 19:45:43 -0000

XMLUnit for Java 2.8.3

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Sun, 10 Oct 2021 16:47:49 -0000

I'm afraid this is due to the way DOM is implemented (in Java?). XMLUnit uses the DOM model when comparing XML files. This means your Java process contains two parsed tree models of the whole documents in memory at the same time - and DOM is famous for being memory intensive. At least you seem to be able to load both documents, so there probably isn't that much memory missing and you could get by with increasing your JVM's heap memory a bit when starting the process. There are alternative APIs for...

Shubham Arvikar posted a comment on discussion Open Discussion

Shubham Arvikar — Wed, 06 Oct 2021 13:43:05 -0000

Hello, I am trying to compare 2 large xml files which contains around 2.4m+ lines (xml file size ~ 51 MB). This is the method I have created where I am sending xmlfilepath for 2 xmls. It is working fine with some small responses but for huge one it is throwing java oom gc error. Is there any limitation of xmlunit? do we have any solution for this type of issue? public static Iterable compareXmlFiles(String response1FilePath, String response2FilePath) throws IOException, SAXException {...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Wed, 30 Jun 2021 05:57:19 -0000

But do you know which elements are expected to hold numbers? If so, you can still use the DifferenceEvaluator approach I described. Otherwise - if you don't know which elements are to be considered numbers how should XMLUnit know? :-)

Jaspreet Singh Ahuja modified a comment on discussion Help

Jaspreet Singh Ahuja — Tue, 29 Jun 2021 18:16:59 -0000

I have to ignore differences such as Expected text value '1.3440000000000001E1' but was '13.44'. I have multiple such nodes with that kind of difference- so I can't predetermine which node will have that kind of values. I wish I had stakeholders like Hari Rao. :'-( , but that isn't the case and would appreciate some help. 11.5 1.3440000000000001E1 some string V/S 11.5 ...

Jaspreet Singh Ahuja posted a comment on discussion Help

Jaspreet Singh Ahuja — Tue, 29 Jun 2021 18:14:07 -0000

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Mon, 22 Feb 2021 19:58:13 -0000

so am I

Swapnil Kotwal modified a comment on discussion Help

Swapnil Kotwal — Mon, 22 Feb 2021 06:01:23 -0000

I'm talking about Map { } inside

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Mon, 22 Feb 2021 06:00:59 -0000

I'm talking about Map { } inside ~~~ ~~~

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Sat, 20 Feb 2021 16:05:54 -0000

You are using ElementSelectors.byNameAndText which means: when looking at lists of elements, compare those which each other that have the same element name and the same nested text. This works fine for elements like S013J6S7STH. In your second example you want to influence which Map elements XMLUnit compares with each other. The Map elements have no nested text at all, so they all have the same nested text and you compare them in-order. I'm not really sure what identifies the Map...

Swapnil Kotwal modified a comment on discussion Help

Swapnil Kotwal — Thu, 18 Feb 2021 12:01:20 -0000

I've used below DiffBuilder using XMLUnit-2 diff = DiffBuilder.compare(control).withTest(test).checkForSimilar() .normalizeWhitespace().ignoreComments() .ignoreWhitespace().ignoreElementContentWhitespace() .withNodeFilter(node -> (filter(node, attrsToIgnore))) .withAttributeFilter(fields -> (filterFields(fields, fieldsToIgnore))) .withNodeMatcher(new DefaultNodeMatcher(ElementSelectors.byNameAndText)).build(); It works well for shuffling the List<> values or random value in List<> as shown below...

Swapnil Kotwal modified a comment on discussion Help

Swapnil Kotwal — Thu, 18 Feb 2021 12:00:25 -0000

I've used below DiffBuilder using XMLUnit-2 diff = DiffBuilder.compare(control).withTest(test).checkForSimilar() .normalizeWhitespace().ignoreComments() .ignoreWhitespace().ignoreElementContentWhitespace() .withNodeFilter(node -> (filter(node, attrsToIgnore))) .withAttributeFilter(fields -> (filterFields(fields, fieldsToIgnore))) .withNodeMatcher(new DefaultNodeMatcher(ElementSelectors.byNameAndText)).build(); ```` It works well for shuffling the `List<>` values or random value in `List<>` as shown...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Thu, 18 Feb 2021 11:59:53 -0000

I've used below DiffBuilder using XMLUnit-2 diff = DiffBuilder.compare(control).withTest(test).checkForSimilar() .normalizeWhitespace().ignoreComments() .ignoreWhitespace().ignoreElementContentWhitespace() .withNodeFilter(node -> (filter(node, attrsToIgnore))) .withAttributeFilter(fields -> (filterFields(fields, fieldsToIgnore))) .withNodeMatcher(new DefaultNodeMatcher(ElementSelectors.byNameAndText)).build(); ```` It works well for shuffling the `List<>` values or random value in `List<>` as shown...

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Mon, 21 Dec 2020 09:12:19 -0000

This release fixes a bug in the new AssertJ 3.x module. CompareAssert inside the AssertJ3 module swapped the expected and actual parameters when creating the assertion error. #210 by @f-lopes

Stefan Bodewig created a blog post

Stefan Bodewig — Mon, 21 Dec 2020 09:11:41 -0000

XMLUnit for Java 2.8.2

Stefan Bodewig created a blog post

Stefan Bodewig — Sun, 15 Nov 2020 12:11:18 -0000

XMLUnit for Java 2.8.1

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Fri, 30 Oct 2020 17:04:38 -0000

XMLUnit 2.8.0 has just been released and allows the TransformerFactory to be set explicitly in DefaultComparisonFormatter.

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Fri, 30 Oct 2020 17:01:51 -0000

Both releases are mostly bugfix releases. Unfortunately both are going to break backwards compatibility for some people. All modules of XMLUnit for Java now require Java7 as a minimum and the optional JAXB dependency has been updated to use the Jakarta XML Binding API. XMLUnit.NET has made ISource disposable which is going to break custom implementations. Details for XMLUnit for Java 2.8.0 changed optional JAXB dependency to use Jakarta XML Binding API PR #186 by @endrejeges bumped the bytebuddy...

Stefan Bodewig created a blog post

Stefan Bodewig — Fri, 30 Oct 2020 17:00:49 -0000

XMLUnit for Java 2.8.0 and XMLUnit.NET 2.9.0 Released

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Sun, 30 Aug 2020 09:56:17 -0000

You don't want to ignore the element at all, you want to ignore certain attributes on them. So AttributeFilter is what you want to use rather than NodeFilter.

Aashay Pilivkar posted a comment on discussion Help

Aashay Pilivkar — Tue, 25 Aug 2020 17:17:49 -0000

Hi, I am facing the same issue. I am trying to compare actual and expected XML responses using Java. For that I am using DiffBuilder. I want to ignore few date-time attributes from root node while comparing the xmls. However when I pass the with NodeFilter(node -> !node.getNodename(). equals("Nodename") ) it ignores complete xml. Could you please let me know the work around for the issue? Thanks in advance.

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Wed, 29 Jul 2020 08:22:41 -0000

I've opened https://github.com/xmlunit/xmlunit/issues/195 and will get to it sometime in the coming weeks. If there is anything else you'd need please open new issues. Thanks Stefan

James Murtaugh posted a comment on discussion Help

James Murtaugh — Tue, 28 Jul 2020 17:00:45 -0000

Hi Stefan, I realize that my patch is not a long term solution to the issue I just did that to make sure that was the root cause of the issue. We are using the library to compare two xml files so we would need a mechanism to allow us to specify the transform factory in the DefaultComparisonFormatter. Please let me know how you would like to proceed. Jim From: Stefan Bodewig bodewig@users.sourceforge.net Sent: Tuesday, July 28, 2020 7:41 AM To: [xmlunit:discussion] 73274@discussion.xmlunit.p.re.sourceforge.net...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Tue, 28 Jul 2020 11:40:37 -0000

Hi Jim I don't use OSGi myself and am not intimately familiar with it. I've tried to setup things in a way, that should allow all modules to be used as OSGi bundles, so supporting the environment is a goal. OTOH we do want to support people switching the TransformerFactory using JAXP mechanisms. It is unfortunate this seems to be incompatible with OSGi. Your patch as you describe it, would hard-code Saxon for everybody, which cannot be a goal at all. I think it is possible to pass a TransformerFactory...

James Murtaugh posted a comment on discussion Help

James Murtaugh — Tue, 21 Jul 2020 20:47:14 -0000

To whom it may concern, We are attempting to use the xmlunit-core library methods in an OSGi application. At runtime, we ran into a situation where the TransformerFactory class was not being resolved. I have included below an explaination of a modification to the xml unit code that we used to address this issue. We are wondering if there is an existing mechanim to address OSGI loading? If not, is there any interest in developing a feature so that we do not have to maintain a separate library with...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Sat, 16 May 2020 05:52:47 -0000

Thanks you Stefan, this will help :) On Tue, May 12, 2020 at 10:27 PM Stefan Bodewig bodewig@users.sourceforge.net wrote: Sorry I was busy elsewhere and forgot to answer here. Starting out with you ElementSelector that would use byNameAndAttributes("key") for entry - and whatever else is needed, you'd only end up with CHILD_LOOKUP differences for things the server has added and CHILD_NODELIST_LENGTH. The later could be downgraded easily in a DifferenceEvaluator using DifferenceEvaluators.downgradeDifferencesToSimilar....

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Tue, 12 May 2020 16:57:39 -0000

Sorry I was busy elsewhere and forgot to answer here. Starting out with you ElementSelector that would use byNameAndAttributes("key") for entry - and whatever else is needed, you'd only end up with CHILD_LOOKUP differences for things the server has added and CHILD_NODELIST_LENGTH. The later could be downgraded easily in a DifferenceEvaluator using DifferenceEvaluators.downgradeDifferencesToSimilar. For the CHILD_LOOKUP you'll have to write a small DifferenceEvaluator yourself which would return EQUAL...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Tue, 12 May 2020 16:50:55 -0000

I'm sorry I have overlooked this question so far. For both platforms XMLUnit's validator is just a thin layer on top of the platform's validation engine, so I'm not surprised you see a difference between .NET and Java. You might even see diffenrences between different version of each. It shouldn't be too difficult to add an optional Predicate as a filter one can specify that could be used to suppress certain failures. Could you please open an enhancement request over at github...

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Tue, 12 May 2020 16:31:35 -0000

These two releases contain an incompatible change to the (I)PlaceholderHandler interface, thus the new minor versions. 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)}. For XMLUnit.NET only the placeholders package has changed, for Java in addition the assertj module is now supposed to be compatible with AssertJ 3.15+. Release Notes for XMLUnit for...

Stefan Bodewig created a blog post

Stefan Bodewig — Tue, 12 May 2020 16:30:57 -0000

XMLUnit for Java 2.7.0 and XMLUnit.NET 2.8.0 Released

Wesley Manning posted a comment on discussion Help

Wesley Manning — Wed, 22 Apr 2020 13:45:12 -0000

Hi, In a unit test I have: Validator val2 = Validator.ForLanguage(Languages.W3C_XML_SCHEMA_NS_URI); val2.SchemaSource = new StreamSource("SettingsXmlSchema.xsd"); ValidationResult result2 = val2.ValidateInstance(new StreamSource(memStream)); Assert.True(result2.Valid); My schema contains a element as the xml document can have extra attributes that I don't control and so don't want to check against in my schema. But XMLUnit ValidationResult"Valid"...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Mon, 20 Apr 2020 07:26:20 -0000

Thanks Stefan, Assume, I have localTestXML as But, server Response can keep on increasing. It might add newer...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Mon, 20 Apr 2020 06:36:12 -0000

I'm sorry if I seem to be a bit slow on this but I believe I still don't undertstand what you actually mean by partial XML data validation. This is waht I'm guessing: You've got a document that describes your tests as a sparse XML document. You are not interested in parts of the server response that are not part of the sparse tree in your document. To achive this, you will need a NodeFilter and may need to combine it with something loke an ElementSelector to figure out which parts of the tree to...

Swapnil Kotwal modified a comment on discussion Help

Swapnil Kotwal — Wed, 15 Apr 2020 13:43:15 -0000

I already have implemented it using CSV but my data is complex so I turned to XMLUnit library. My server can returns data of 100s of Users/Groups etc and I've to validate some of them. Considering above given XML, I can specify data into CSV as below identity,accountFlags,homePhone "FooBar",(Not_to_Validate),6555 "FooBar1",["list data1","list data2"],6555 Here , you can notice, in first row of CSV 1. I mentioned only very few partials entrys to validate and also ignored (filtered out) accountFlags=(Not_to_Validate)....

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Wed, 15 Apr 2020 13:40:34 -0000

Swapnil Kotwal modified a comment on discussion Help

Swapnil Kotwal — Wed, 15 Apr 2020 13:37:04 -0000

My XML is little complex and I've to ignore certain entry from the comparison, how would I able to achieve it ? Normal User Account Password Cannot Expire ...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Wed, 15 Apr 2020 12:56:19 -0000

I'm afraid this is something that is easier to do for humans than to implement in code. When you look at the serverResponseXML how do you know which parts you want to compare and which are not necessary? Is it as simple as "any element that's not in localTestXML is irrelevant" or could this hide errors of extra elements suddenly appearing in unexpected places?

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Wed, 15 Apr 2020 10:53:10 -0000

Thanks Stefan for the response. Sorry, I'm just putting baby steps and messed up certain things. From serverResponseXML I might have some entrys I want to ignore during comparison and I might specify partial localTestXML which not necessarily should have all entrys from serverResponseXML (i.e. I want to validate with partial local XML(It can be partial XML or as complete as serverResponseXML) with some additional filters) What would be best way to achive it?

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Mon, 13 Apr 2020 17:15:13 -0000

assuming https://sourceforge.net/p/xmlunit/discussion/73274/thread/b01a104e75/#6e65 was meant to go here: You really need to answer to yourself what it is that makes you know which entrys to compare to each other. Don't thnk in terms of XPaths, think in terms of your logical data model. And once you've understood what is important in your data model, then - and only then - start thinking about how this translates to XML structure. It is not unlikely that implementing a NodeFilter or ElementSelector...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Mon, 13 Apr 2020 17:09:16 -0000

maybe your question was supposed to be added to https://sourceforge.net/p/xmlunit/discussion/73274/thread/5481136c30/ instead?

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Mon, 13 Apr 2020 17:06:50 -0000

I don't know the XML you are trying to comapre. The difference you mention says there are different numbers of elements nested in Map between control and test. I have no idea how this relates to XPath. Most probably I'm missing some context that you have :-)

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Mon, 13 Apr 2020 17:03:39 -0000

checkForSimilar and checkForIdentical are mutually exclusive and the las one you set wins. Unless you you provide a DifferenceEvaluator that downgrades node order differences to IDENTICAL you will never get better than SIMILAR with swapped nodes. So if you are really aiming for an identical result you will need to override the DifferenceEvaluator in use as well. The ElementSelector's job is to make XMLUnit match the nodes with each other that you consider to be "the same nodes", it does not make...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Mon, 13 Apr 2020 13:40:56 -0000

Thanks Stefan, This worked as expected but still I'm getting error as Expected child nodelist length '22' but was '21' - comparing at /ResourceObject[1]/Attributes[1]/Map[1] to at /ResourceObject[1]/Attributes[1]/Map[1] [java] Expected child 'entry' but was 'null' - comparing at /ResourceObject[1]/Attributes[1]/Map[1]/entry[23] to } For , diff = DiffBuilder .compare(control) .withTest(test) .checkForSimilar().checkForIdentical() .normalizeWhitespace() .ignoreComments()...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Mon, 13 Apr 2020 11:02:51 -0000

I've a XML as below Normal User Account Password Cannot Expire

Swapnil Kotwal modified a comment on discussion Help

Swapnil Kotwal — Sat, 11 Apr 2020 10:04:29 -0000

My XML is little complex and I've to ignore certain entry from the comparison, how would I able to achieve it ? Normal User Account...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Sat, 11 Apr 2020 09:48:19 -0000

Thank you for the clarification Stefan On Sat, 11 Apr, 2020, 2:17 PM Stefan Bodewig, bodewig@users.sourceforge.net wrote: Neither accountFlags nor homePhone are element names, so your filter will not match anything. Your NodeFilter must return true unless all of the following conditions are met node is actually an Element node has an attribute named "key" the value of this attribute is either accountFralgs or homePhone private boolean filter(final Node n) { if (n instanceof Element) { final String...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Sat, 11 Apr 2020 09:12:05 -0000

Thanks 😊, it makes sense. On Sat, 11 Apr, 2020, 2:07 PM Stefan Bodewig, bodewig@users.sourceforge.net wrote: Well, you do know the elements you are interested in, so you could easily do final Collection expected = Arrays.asList("root", "elementA", elementB", "elementC"); ... .withNodeFilter(n -> expected.contains(n.getNodeName())) XMLUnit-2 compare partial XMLs https://sourceforge.net/p/xmlunit/discussion/73274/thread/b01a104e75/?limit=25#4e1a Sent from sourceforge.net because you...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Sat, 11 Apr 2020 08:47:50 -0000

Neither accountFlags nor homePhone are element names, so your filter will not match anything. Your NodeFilter must return true unless all of the following conditions are met node is actually an Element node has an attribute named "key" the value of this attribute is either accountFralgs or homePhone private boolean filter(final Node n) { if (n instanceof Element) { final String attrValue = ((Element) n).getAttibute("key"); // attrValue is th eempty string if the attribute is missing return !("accountFlags".equals(attrValue)...

David Alexis Vargas Álvarez posted a comment on discussion Help

David Alexis Vargas Álvarez — Sat, 11 Apr 2020 08:37:47 -0000

Thanks for all the help provided! I finally decided to use the "separate comparisons" approach, here's a short example of what I've done, hopefully this helps someone in the future: private static readonly ComparisonType[] ExcludedComparisons = new ComparisonType[] { ComparisonType.CHILD_NODELIST_LENGTH }; private static readonly DifferenceEvaluator DiffEvaluator = DifferenceEvaluators.DowngradeDifferencesToEqual(ExcludedComparisons); public bool CompareNodesByXPath(params string[] nodeXPaths) {...

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Sat, 11 Apr 2020 08:37:23 -0000

Well, you do know the elements you are interested in, so you could easily do final Collection expected = Arrays.asList("root", "elementA", elementB", "elementC"); ... .withNodeFilter(n -> expected.contains(n.getNodeName()))

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Fri, 10 Apr 2020 12:01:09 -0000

My XML is little complex and I've to ignore certain entry from the comparison, how would I able to achieve it ? Normal User Account...

Swapnil Kotwal posted a comment on discussion Help

Swapnil Kotwal — Fri, 10 Apr 2020 11:59:11 -0000

I have a local test XML data as below testLocalXML something different something else yet another thing but the data I'm getting from server could be large and will keep dynamically increasing e.g. Server Response something different something else yet another thing next data another data F data...

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Sun, 08 Mar 2020 14:25:14 -0000

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 when NodeFilters 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...

Stefan Bodewig created a blog post

Stefan Bodewig — Sun, 08 Mar 2020 14:24:11 -0000

XMLUnit for Java 2.6.4 and XMLUnit.NET 2.7.2 Released

Stefan Bodewig posted a comment on discussion Help

Stefan Bodewig — Mon, 03 Feb 2020 06:39:49 -0000

For your second problem there is no built-in solution in XMLUnit. For XMLUnit attribute values are strings and as such your attributes are clearly different. But XMLUnit offers an extension point, you can provide your own custom DifferenceEvaluator that would alter the outcome of ATTR_VALUE differences if they looked like numbers. The example in https://github.com/xmlunit/user-guide/wiki/DifferenceEvaluator shows how to react only to differences on attributes. The best way to use your own DifferenceEvaluator...

Reddy posted a comment on discussion Help

Reddy — Fri, 31 Jan 2020 13:19:40 -0000

Found solution for first part of the above question diff = DiffBuilder.compare(testxml) .withTest(resxml) .withNodeMatcher(new DefaultNodeMatcher(ElementSelectors.conditionalBuilder().whenElementIsNamed("ShiftAttribute").thenUse(ElementSelectors.byNameAndAttributes("ShiftAttributeCode")).elseUse(ElementSelectors.byName).build())) .build();

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:22:34 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea VS Also, please help me ignoring below differences

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:22:10 -0000

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:20:08 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me ignoring below differences

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:19:36 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me ignoring below differnce

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:19:34 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me ignoring below differnce

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:18:40 -0000

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:18:15 -0000

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:18:00 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me in ignoring below differnce

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:17:36 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me for skip/ignore below differnce

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:17:13 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me to skip/ignore below differnce

Reddy modified a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:16:51 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me to ignore/skip below differnce

Reddy posted a comment on discussion Help

Reddy — Thu, 30 Jan 2020 22:15:11 -0000

How to ignore below element order in XMLUnit2, I find something in XMLUnit1, but trying to do in XMLunit2, please let me know if any one have any idea vs Also, please help me to ignore below differnce

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Tue, 02 Jul 2019 08:41:28 -0000

I don't think there is an easy way to do what you need without changing XMLUnit. You might gain a bit of performance by using a single XPathFactory and a single XPath instance, though. Something that might work is tracking what the difference engine is doing via a ComparisonListener and building a map of XPath to Node while the DOM is traversed. Adding the parent nodes in addition to the parent XPath would require some surgery to DOMDifferenceEngine but could probably be done without breaking the...

MonishaM modified a comment on discussion Open Discussion

MonishaM — Thu, 27 Jun 2019 21:45:09 -0000

In our project, we are comparing two XMLs and are selectively updating the control XML based on this comparison. In certain cases the Control/Test node is null (as fetched from the Comparison.Detail object). Manipulating / updating the Control/Test XML in such a case requires us to compute the Parent Node using some other library that requires the XPath String from the getParentXPath() method. This computation of the Parent Node node is turning out to be expensive as we need to do this for every...

MonishaM posted a comment on discussion Open Discussion

MonishaM — Thu, 27 Jun 2019 21:44:08 -0000

Hi Stefan, We had another question for you. Currently, we can only access the XPath of the ParentNode of a given target node (computed from the Comparison.Detail object). Is there a way to get a reference to the ParentNode directly from the Comparison.Detail object? Or atleast in a future version of XMLUnit? Have opened a new Discussion Topic for this here. Please advise.

MonishaM posted a comment on discussion Open Discussion

MonishaM — Thu, 27 Jun 2019 21:39:15 -0000

MonishaM posted a comment on discussion Open Discussion

MonishaM — Fri, 21 Jun 2019 19:41:33 -0000

Hi Stefan, We tested using 2.6.3 and it worked fine. This time the XPaths were preserved despite using NodeFilters in the Difference Evaluator. Thank you very much for such an expedited response and fix! This has been very helpful.

Stefan Bodewig posted a comment on discussion Open Discussion

Stefan Bodewig — Fri, 21 Jun 2019 19:04:58 -0000

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 Issue #153 via PR #154 by @NathanAtClarity. the XPath values of a comparison should not be affected by any NodeFilter being in effect. Issue #156