[
https://issues.apache.org/jira/browse/DAFFODIL-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-2410.
--------------------------------------
Resolution: Duplicate
Controlling this for warnings was implemented in DAFFODIL-864 and for
validation errors in DAFFODIL-2927.
By default unexpected warnings and validation errors are still ignored for
backwards compatability. But the default can be changed globally by setting
defaultIgnoreUnexpectedWarnings/ValidationErrors, or per test by setting
ignoreUnexpectedWarnings/ValidationErrors.
> TDML Runner hides warnings and validation errors
> ------------------------------------------------
>
> Key: DAFFODIL-2410
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2410
> Project: Daffodil
> Issue Type: Improvement
> Components: TDML Runner
> Reporter: Steve Lawrence
> Priority: Minor
> Labels: beginner
>
> The TDML Runner currently hides warnings. This means that if we make a change
> that causes many new warnings it is very easy to not realize it.
> Unfortunately, many tests, including those external to daffodil, might rely
> on this current behavior so we can't simply fail tests if warnings exist but
> there are no tdml:warnings in the TDML test.
> However, we should at least have some mode that allows us to run the TDML
> runner and error if there are unchecked warnings. Or perhaps we always output
> warnings, which would encourage users to update their schemas or fix tests to
> suppress expected warnings. We could even provide a message that says in some
> future release uncheck warnings will always be considered an error if we want
> to go that route.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
