Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: How to Compare DOMs for Unit Tests?

From: "Joe Fawcett" <joefawcett@---------.------>
To: NULL
Date: 12/24/2008 10:00:00 AM

"Siegfried Heintze" <siegfried@h...> wrote in message 
news:u0yUsfUZJHA.1272@T......
> I'm using Microsoft C++ V15 to serialize DOMs to disk using MSXML.
>
> I want to write some unit tests to verify that I am producing the same 
> DOMs. I might use SAX in the future.
>
> Should I compare XML files? Is there a tool to do this so that it 
> appropriately ignores white space? Or should I deserialize the standard 
> XML file into a DOM and compare it with my in memory copy? Uggh, that 
> sounds ugly!
>
>
> Thanks,
> Siegfried
>
It's not a trivial task as you need to compare at the infoset level rather 
than as a file compare.
(For example <node att="1"/> is the same as <node att='1' /> at the infoset 
level but not at the file level.)
XmlDiff can be used manually, I don't know if it has an API though.

-- 

Joe Fawcett (MVP - XML)
http://joe.fawcett.name 



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent