Thanks !! Nice suggestion ! We also thought of this option but it is not that much convincing because we want to check a new system (xerces) with the existing system(libxml2).
Using new system (xerces) to process the existing (libxml2) response and then again mapping it with the new system may not be the ideal testing strategy, hence wanted to know if there is a workaround possible. - Thanks, Aachin On Thu, Jan 16, 2014 at 2:16 PM, Mathieu Champlon < mathieu.champ...@masagroup.net> wrote: > On 16/01/2014 07:38, Aachin Chalana wrote: > >> Thanks for the reply !! >> >> I would like to explain the need in details. >> >> We have an existing writer/parser implementation that uses libxml2. we are >> working on a corresponding c++ implementation. >> Since the existing code is critical so as a test strategy we decided to >> match the outcomes of the two implementations (because manually comparing >> complete xmls will require humungous effort). >> >> The issue is that the attributes in the xml formed by using libxml2 are >> not >> ordered, but they are ordered in xerces hence the test cases fail. >> >> - >> Thanks, Aachin >> > > Hi, > > Maybe you could simply reload and rewrite with xerces your documents > created with libxml2 ? > I believe there's a demo application in xerces which does more or less > that already. > > Cheers, > MAT. >
