Hi @StJabin
Did that issue occure in utPLSQL v3.10 ?
This is quite old version and lot of fixes has been done in between.
Also if it does.
Could you provide a test case to replicate.

Hi Iwasylow, thanks for replying!

I've repeated the test with UTPLSQL v3.1.10.3349. It shows the same behavior.

This is the test case:

PROCEDURE raiseExc
IS
v NUMBER;
BEGIN
ut.expect(1).to_equal(0);
v := 3 / 0;
END;

Output when I use default reporter (ut_documentation_reporter):
Failures:

1. raiseexc
   ORA-01476: divisor is equal to zero
   ORA-06512: at "METI2TDS.TSTUTOPSFINISHPES", line 1129
   ORA-06512: at "METI2TDS.TSTUTOPSFINISHPES", line 1129
   ORA-06512: at line 6
   Actual: 1 (number) was expected to equal: 0 (number)
   at "METI2TDS.TSTUTOPSFINISHPES.RAISEEXC", line 1128 ut.expect(1).to_equal(0);

Output when I use ut_junit_reporter:

<error>
<![CDATA[
ORA-01476: divisor is equal to zero
ORA-06512: at "METI2TDS.TSTUTOPSFINISHPES", line 1129
ORA-06512: at "METI2TDS.TSTUTOPSFINISHPES", line 1129
ORA-06512: at line 6
]]>
</error>

Thanks, if you can have a look on it!

Seems that error/failure reporting in JUnit reporter are mutually exclusive today.
That could be changed and we could report both.
Need to check if there are no restrictions on this from the format standard perspective.