[
https://issues.apache.org/jira/browse/DAFFODIL-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Beckerle closed DAFFODIL-1384.
--------------------------------------
Resolution: Duplicate
Fix Version/s: (was: deferred)
Closing as this duplicates DAFFODIL-288 and DAFFODIL-1846 which taken together
cover this general topic of being strict in comparisons in the TDML runner.
> TDML Runner: Strict Comparison Mode
> -----------------------------------
>
> Key: DAFFODIL-1384
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1384
> Project: Daffodil
> Issue Type: Improvement
> Components: Infrastructure, TDML Runner
> Reporter: Jessie Chab
>
> Note from Mike:
> Our TDML runner and other unit test rigs we use, compare the resulting
> infosets in a way that strips off all attributes, and all namespace prefixes.
> This was done for expediency, because earlier versions of Daffodil were not
> doing elementFormDefault and getting all the namespace prefix definitions
> minimized and such, so we were getting false negative comparisons.
> I guess we need a mode which turns this off so tests can be more rigid than
> this in comparison. There may be a JIRA ticket for this already.
> One thing for us to consider is getting an XML-comparison 3rd party library.
> This issue of comparing XML in a way that is not sensitive to how namespaces
> are prefixed so long as they are the right namespaces, has already been
> solved.
> -------------------------
> In order to fully test DFDL-1330, we need the ability to perform this strict
> comparison, so we can verify when namespace prefixes are present in the
> result.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
