liuml07 opened a new pull request, #27092: URL: https://github.com/apache/flink/pull/27092
https://issues.apache.org/jira/browse/FLINK-38488 Currently we have some tests using following patter: ```java try { doTestSomething(); ... } catch (Exception e) { e.printStackTrace(); fail(e.getMessage()); } ``` This can be replaced by just throwing Exceptions in test and let JUnit handles the failure along with exception stack trace. The existing code loses stack trace information in test reports, and we need to look around in the stdout to guess. As we can see other tests in Flink uses the "throws Exception" model: - The framework provides better formatting and integration with IDEs and CI systems - Test runners can distinguish between assertion failures and unexpected exceptions - Test logic is more readable without exception handling noise -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
