michael-hoke commented on issue #811: URL: https://github.com/apache/daffodil-vscode/issues/811#issuecomment-1785704290
Our main use case for TDML is posting test cases (presumably ones that fail to parse) on the user list. It would make sense to be able to attach a stack trace to a test case so that someone can verify their stack trace against the "expected" one that is being reported. I'm not actually sure where this idea originated from, but we've been floating it around for quite some time as a nice to have feature for our users list scenario. Maybe I was assuming that a stack trace could be considered an output for a test case? eg. If I wanted to capture a daffodil parse that I expect to fail and compare the expected/actual stack traces. We are planning to look into an automated way of producing a zip archive containing all artifacts required to run all test cases in a TDML file, so maybe it will make more sense to include the stack trace as a separate artifacts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@daffodil.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
