Re^2: XML parser

The long description is that I'm making a test system. The xml file is used for both configuration and saving the results in.
The first part is that a WEB-GUI is saving witch tests to run.

<exec>
   <tc id=001></tc>
   <tc id=002></tc>
</exec>
[download]

Second will the testframework append testinfo to the different nodes and add childs to the nodes.

<exec>
   <tc id=001 desc=first test>
      <ts id=001.001 result=passed/>
   </tc>
   <tc id=002 desc=second test>
      <ts id=002.001 result=failed/>
   </tc>
</exec>
[download]

So the testframework has to be able to find the specific node by using the id and append info/data and child to that node.
Does anyone have any suggestions how to do this?

Comment on Re^2: XML parser Select or Download Code

Replies are listed 'Best First'.
Re^3: XML parser by toma (Vicar) on Nov 30, 2007 at 08:45 UTC
Do you want the output file to have the same order of XML tags as the input file? I built an automated test equipment (ATE) configuration and test system using XML::Simple, but I didn't like it because it changed the order of the XML tags between the input and the output. I switched from XML::Simple to XML::Twig and solved this problem. After doing this, I thought that maybe XML is not so great for this type of application. I wanted human-readable files that were also easy to parse with a computer. I also wanted to add tags in the future without breaking old files. XML seemed like the right choice but it was not so easy to achieve these goals. Recently I have tried YAML with the same goals, but this has not been so great, either. I am still looking for a better solution. Now I think I should use something like YAML, but I should write my own parser. It should work perfectly the first time! - toma	[reply]

Replies are listed 'Best First'.

Re^3: XML parser
by toma (Vicar) on Nov 30, 2007 at 08:45 UTC

I built an automated test equipment (ATE) configuration and test system using XML::Simple, but I didn't like it because it changed the order of the XML tags between the input and the output. I switched from XML::Simple to XML::Twig and solved this problem.

After doing this, I thought that maybe XML is not so great for this type of application. I wanted human-readable files that were also easy to parse with a computer. I also wanted to add tags in the future without breaking old files. XML seemed like the right choice but it was not so easy to achieve these goals. Recently I have tried YAML with the same goals, but this has not been so great, either. I am still looking for a better solution.

Now I think I should use something like YAML, but I should write my own parser.

It should work perfectly the first time! - toma

[reply]