[
https://issues.apache.org/jira/browse/DAFFODIL-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742094#comment-17742094
]
Olabusayo Kilo commented on DAFFODIL-2694:
------------------------------------------
I'll PR the changes for trace.
It's similar, but not the same. For parsing, we use withDebugger(id) on the
processor directly. Whereas for testing, we're not using the DataProcessor like
in parsing, instead we're using the TDMLRunner and setDebugger(id)
> CLI -t trace option doesn't work for daffodil test commands in TDML
> -------------------------------------------------------------------
>
> Key: DAFFODIL-2694
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2694
> Project: Daffodil
> Issue Type: New Feature
> Components: TDML Runner
> Affects Versions: 3.3.0
> Reporter: Mike Beckerle
> Assignee: Olabusayo Kilo
> Priority: Major
>
> This command does not cause tracing:
> {code:java}
> daffodil -t test -iii src/test/resources/owl/myTests.tdml testName
> {code}
> It is important and very convenient when using CLI and TDML to be able to
> trace a single test.
> The general -t (for trace) option should apply to running TDML as well as
> parse/unparse.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
