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

Existing state of packages was discarder #504

Closed
jgebal opened this Issue Oct 26, 2017 · 2 comments

Comments

2 participants
@jgebal
Copy link
Member

jgebal commented Oct 26, 2017

If utPLSQL encounters ORA-04068 or ORA-04061, it will immediately abort test execution and re-raise the exception.

This mechanism is implemented deliberately as supressing this exceptions makes the session unable to re-validate the invalid package state.
If ut_executable would suppress those exceptions, consecutive calls to ut.run() would still end with invalid package state.

When running a suite of more than one test package, the side effect is that not all tests get executed and the results are partly presented on the outputs as the execution is aborted.

As an alternative the framework could flag such exceptions when they occur, so it can continue with execution for the remaining of unit test packages.
If the exception was flagged, the framework would throw an exception after the execution.
That way we allow the session to recover from invalid package state and still run a full suite.

@jgebal jgebal added the enhancement label Oct 26, 2017

@jgebal jgebal added this to the v3.1.0 milestone Oct 26, 2017

@Shoelace

This comment has been minimized.

Copy link
Member

Shoelace commented Dec 17, 2017

so to clarify, it essentially just becomes another failure reason ?

@jgebal

This comment has been minimized.

Copy link
Member Author

jgebal commented Dec 18, 2017

Almost, except that we have to throw the right type of exception. It still needs validation. I'm not sure if it will work properly when you manually throw such exception post execution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.