For TestNG tests that expect exceptions, TestNG does not report the stack trace in the log file.
When reading the Jtreg log files the stacktrace output can at first glance appear to be a failure.
Since the exception is expected, the complete stack trace is not needed.
Perhaps the exception message would be useful but should be identified as the expected/success value.
When reading the Jtreg log files the stacktrace output can at first glance appear to be a failure.
Since the exception is expected, the complete stack trace is not needed.
Perhaps the exception message would be useful but should be identified as the expected/success value.
- relates to
-
CODETOOLS-7900112 don't print unnecessary stack traces
-
- Resolved
-