How can I trap Oracle errors in script assertion

Hello,

I run into the same problem.

My JDBC Test Step does query a table that obviously does not exist in the database.

I have a "JDBC Status" assertion but it is not evaluated and the Test Case does not turn RED.

The only place I can see things went wrong is when I open the log pane at the bottom of ReadyAPI.

How can I add an assertion that checks that the query could be run ?

What is the aim of the "JDBC Status" if this does not cover such case ?

Thanks in advance for your help.

Pierre