[
https://issues.apache.org/jira/browse/DAFFODIL-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820178#comment-17820178
]
Steve Lawrence commented on DAFFODIL-2878:
------------------------------------------
ExpectIOException has a "getInputBuffer" function which I think returns a
string represents what expect is trying to match. Should be a small change.
In the mean time, you should be able to add {{debug = true}} as a parameter to
the to the runCLI function for your test. That will output the CLI command and
echo CLI input and output to stdout.
> cli test expect timeouts need to display the captured text that doesn't meet
> the expectation
> --------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-2878
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2878
> Project: Daffodil
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: 3.6.0
> Reporter: Mike Beckerle
> Priority: Minor
>
> When a CLI test fails due to an expect timeout such as:
>
> {code:java}
> [error] Test
> org.apache.daffodil.cli.cliTest.TestCLIParsing.test_Layer_Execution_Error
> failed: net.sf.expectit.ExpectIOException: Expect operation fails (timeout:
> -1 ms) for matcher: contains('Unexpected exception in layer transformer
> 'buggy''), took 3.414 sec
> [error] at net.sf.expectit.ExpectImpl.expectIn(ExpectImpl.java:106)
> {code}
> It could be good if the actual output text was displayed so that one can see
> why the expectation was not met.
> Without that, it's actually a bit tedious to reproduce the test in order to
> see the actual output. You have to stage daffodil, mine the command line with
> all args from the CLI test, and then issue the command line to daffodil.
> It's not so easy to debug into the expect utility to find the text at issue.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
