[FLINK-38488][tests] Use 'throws Exception' instead of try-catch-fail…

[liuml07]

https://issues.apache.org/jira/browse/FLINK-38488

Currently we have some tests using following patter:

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

[liuml07]

@ruanhang1993 I know you are tracking some testing improvements. Could you review this? Thanks,

[flinkbot]

CI report:

• 3e1301d Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[liuml07]

The testing failure seems unrelated as FLINK-38408 tracks the MapStateNullValueCheckpointingITCase which is not frequently reproducible. Meanwhile, e2e tests are failing with system error as in other builds.

[ruanhang1993]

LGTM. I think throw Exception is enough and better.

[ruanhang1993]

@liuml07 Could you rebase the master branch and re-run the CI? The e2e tests have been fixed. Thanks.

[ruanhang1993]

@flinkbot run azure