Fix Exception Flow Control - Update Trap Comparison (Issue 1175)

[A1K28]

• add test for input
  Closes [Bug]: Incorrect Exception Control Flow Analysis for Nested Try-Catch Blocks (1.3.0) #1175

[swissiety]

lets add a test (input is already pushed) that checks that the correct exceptional successor is linked. for simplicity sth like graph.getBlocks().stream().filter(b -> b.toString().contains("return o")).findFirst().get().getExceptionalSuccessors().values().stream().filter(ehb -> ehb.toString().contains("return 2")).findAny() == true; (beware: its possible the exceptionhandler consists of multiple blocks)

[A1K28]

@swissiety I've added the test as you requested. It's not completely generic, but it should suffice. Let me know if you want me to change anything.

[swissiety]

Wow thats a lot of assertions. Thank you for the testcase!

[swissiety]

Please annotate it with the test category tag (see other tests with java8 something something)

[swissiety]

Please execute the coveo plugin with the fmt goal to apply the code style before committing

[A1K28]

i think i did. not sure if that's what you wanted

[swissiety]

Good work @A1K28 👍