RE: Test suite output format

Hi Felix, all,

Yes, you assumed right. Your example is what I had in mind.

I think a tab-delimited output would be easier to compare with simple diff tools. It would allows implementers to use the same files for their unit tests, making the validation enforced automatically at each build.

We would also need to sort the entries of the attribute items I think. XML parsers have no requirement to present attribute in a specific order and they do it differently. We could sort alphabetically for example.

When a data category has several pieces of information, we should always output them in the same order, even when absent/empty.


> Some questions are:
> - would the output be written with ITS namespaces, e.g. its:translate="yes" vs. "translate="yes"

Either way would be fine.


> - do we need the other information in XML file, e.g. "new value global" etc? I'd say no, just asking

+100. I think not having outputType in that format would also help *a lot*.
I was going to post an email about it :)
That information is actually not useful in production. It may help debugging, but production tools may be designed to optimize the tree decoration to allow for larger documents, and not have this available. After all outputType doesn't test the result, but how you obtained the result.

Cheers,
-yves

Received on Friday, 31 August 2012 12:02:11 UTC