You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2020/11/18 05:55:00 UTC

[jira] [Commented] (DAFFODIL-1299) TDML Runner not checking uniqueness constraints on test case names

    [ https://issues.apache.org/jira/browse/DAFFODIL-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234275#comment-17234275 ] 

Mike Beckerle commented on DAFFODIL-1299:
-----------------------------------------

changing so that TDML Runner explicitly checks for duplicate test names now, and fails if there are any.

(No longer tolerates them, using the first one.)

> TDML Runner not checking uniqueness constraints on test case names
> ------------------------------------------------------------------
>
>                 Key: DAFFODIL-1299
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1299
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Infrastructure, TDML Runner
>    Affects Versions: 1.0.0
>            Reporter: Mike Beckerle
>            Priority: Major
>
> The tdml.xsd has uniqueness constraints for the test case names.
> However, looking at the TestDFDLExpressions.scala, which uses Functions.tdml, if you modify to turn on validation of the tdml file, it reports no problems.
> Yet there are a bunch of duplicates in Functions.tdml (see DFDL-1298). 
> So perhaps some validator option has to be turned on (full schema checking ??) for Xerces to actually check these? Or perhaps those key constraints are simply not correctly expressed and so they aren't enforcing anything.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)