Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Driver exception escalation #43

Open
svettwer opened this issue Jun 14, 2019 · 0 comments
Open

Driver exception escalation #43

svettwer opened this issue Jun 14, 2019 · 0 comments

Comments

@svettwer
Copy link
Contributor

Extracted from #42 (comment)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant