On Tue, 11 Mar 2008, slowjoe <[EMAIL PROTECTED]> wrote: > Is the expectation to get a message like > "Element <c0...> at location /a0[1]/b0[1]/c0[1] in the > control document does not have a match in the test > document." > wrong?
Yes and no. You would get it if c0 is a child of b0 in your control document and b0 has no children at all in your test document. If there are children that haven't been matched yet, you will get a difference talking about nodes that don't match. Just like you do > > If I get a message like "Expected node type '1' but was '8' - > comparing <c0...> at /a0[1]/b0[1]/c0[1] to <!-- some comment --> > at /a0[1]/b0[1]/comment()[1]", do I have to interpret this as > there is no <c0...> in the test document that matches > /a0[1]/b0[1]/c0[1] in the control document? It means "there is no c0 in the test document that matched the c0 of the control document (after consulting the ElementQualifier to find a matching node), but there is a comment node as child of b0 in the test document at the position where c0 is in the control document". > This time I try to disguise my proof of concept as a PDF file, which > needs to be renamed to "xmlunit_issue.zip". I'll look into it later today. Stefan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Xmlunit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xmlunit-general
