When a SUT interacts with the driver and this interaction leads to an exception, it is hard not possible to identify this in a test case. Nor is it possible to make the exception transparent at all, das the exception is part of the SUTs log, which is not in scope of the Citrus test case, suite or general setup.
Therefore, I propose to escalate exceptions to and endpoint of the Citrus JDBC Server and then pass the exception into the test case, so that an issue during driver interaction is escalated to the test case through the JDBC Server.
Extracted from https://github.com/citrusframework/citrus-db/pull/42#discussion_r291943588
When a SUT interacts with the driver and this interaction leads to an exception, it is hard not possible to identify this in a test case. Nor is it possible to make the exception transparent at all, das the exception is part of the SUTs log, which is not in scope of the Citrus test case, suite or general setup.
Therefore, I propose to escalate exceptions to and endpoint of the Citrus JDBC Server and then pass the exception into the test case, so that an issue during driver interaction is escalated to the test case through the JDBC Server.
BR, Sven