Recent changes to bugs

#46 1.2 bug comparing missing attributes

Stefan Bodewig — Sat, 02 Dec 2017 13:49:58 -0000

Harikesh, please don't comment on unrelated closed issues but create a new one if you think you've found a bug.

In your case the NullPointerException probably stems from your comparator. Most likely there is a difference about an unmatched node (there is a text child node of secondChild in the control document but none in the test document). In the case of "missing nodes" one detail side of the Difference is null - which is the intended and documented behavior and so getTestNodeDetail() may be null and getTestNodeDetail().getNode() throws an exception.

#46 1.2 bug comparing missing attributes

Harikesh Kumar — Sat, 02 Dec 2017 06:19:11 -0000

Difference camparison fails when an element value is updated to null.
Sample1: <root><firstChild>first</firstChild><secondChild>secondChild</secondChild></root>
Sample2: <root><firstChild>first</firstChild><secondChild></secondChild></root>

Diff diff = new Diff(oldXml, newXml);
DetailedDiff detDiff = new DetailedDiff(diff);
List<Difference> differences = detDiff.getAllDifferences();
Collections.sort(differences, new Comparator<Difference>() {
@Override
public int compare(Difference o1, Difference o2) {
int i = o2.getTestNodeDetail().getNode().compareDocumentPosition(o1.getTestNodeDetail().getNode());
if(i == 2 || i == 8)
return -1;
else
return 1;
}
});

        It throws NullPointerException at Collections.sort(....) method.

#53 DifferenceEngine error

Stefan Bodewig — Wed, 22 Nov 2017 12:15:32 -0000

I'm not sure what kind of update you exptected. The issue has been closed. I think we are only trying to figure out how to configure the difference engine to create the result you want it to produce, which is not a bug in XMLUnit.

The comparison result you show doesn't match your example XML as it talks about Banana and your examples don't contain any Banana elements.

In order to help you configuring XMLUnit correctly I'd need to know which result you would expect as correct in your case. If you tried XMLUnit 2.x already, I'd urge you to read https://github.com/xmlunit/user-guide/wiki/SelectingNodes

#53 DifferenceEngine error

Stefan Bodewig — Wed, 22 Nov 2017 11:38:42 -0000

Is there any update on the issue mentioned in the above post w.r.t change in the order of the Attribute values as below. I have tried with both XMLUnit 1 & 2 versions with no luck. Any help will be appriciated.

CONTROL
<Fruits>
<Apple size="11" color="green"/>"
<Apple size="13" color="green"/>"
<Apple size="15" color="green"/>"

</Fruits>

TEST
<Fruits>
<Apple size="13" color="green"/>
<Apple size="11" color="green"/>
</Fruits>

Disabling the comparison of unmatched nodes and using ElementNameQualifier class, I got these differences:

Expected attribute value '11' but was '13' - comparing <Apple size="11" ...=""> at /Fruits[1]/Apple[1]/@size to <Apple size="13" ...=""> at /Fruits[1]/Apple[1]/@size
Expected attribute value '13' but was '11' - comparing <Apple size="13" ...=""> at /Fruits[1]/Apple[2]/@size to <Apple size="11" ...=""> at /Fruits[1]/Apple[2]/@size
Expected presence of child node 'Apple' but was 'null' - comparing <Apple...> at /Fruits[1]/Apple[3] to at null
Expected attribute value '10' but was '11' - comparing <Banana size="10" ...=""> at /Fruits[1]/Banana[1]/@size to <Banana size="11" ...=""> at /Fruits[1]/Banana[1]/@size

#48 Respect comments in prelude when checking for identity

Stefan Bodewig — Fri, 06 Feb 2015 20:55:25 -0000

status: open --> closed-fixed

#48 Respect comments in prelude when checking for identity

Stefan Bodewig — Fri, 06 Feb 2015 20:54:54 -0000

it turns out XMLUnit 2.x already detects differences in a document's prelude.

#63 Calling .toString() on Diff runs .compare()

Stefan Bodewig — Wed, 31 Dec 2014 11:36:48 -0000

status: pending-fixed --> closed-fixed

#63 Calling .toString() on Diff runs .compare()

Stefan Bodewig — Tue, 30 Dec 2014 05:39:59 -0000

status: open --> pending-fixed
Group: Java 1.5 --> Java 1.6

#39 testURIResolverForStylesheet fails with JDK >=1.5

Stefan Bodewig — Mon, 29 Dec 2014 16:05:36 -0000

status: open --> closed-out-of-date

#51 xml file comparison fails

Stefan Bodewig — Mon, 29 Dec 2014 16:04:27 -0000

status: pending-invalid --> closed-invalid
Group: --> Java_1.2