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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After execution of ut.run, when I look into v$session to look at my session, it still indicates that my session is running utPLSQL. All the information about application connected (like SQLdeveloper/SQLPlus/jdbc client is lost forever.
The only way to recover is to reconnect.
Provide version info
It's been there for a long time
Expected behavior
having information about currently running utPLSQL test / package is very valuable however it should be handled differently.
utPLSQL should grab information about application info before it starts and should recover that information when it finishes.
We could use events mechanism to trigger registration of application context and send it into application_context event handler so we could:
grab and hold application context before run,
set new context on every before... event
recover grabbed context on after_run event
The text was updated successfully, but these errors were encountered:
Describe the bug
After execution of
ut.run
, when I look into v$session to look at my session, it still indicates that my session is running utPLSQL. All the information about application connected (like SQLdeveloper/SQLPlus/jdbc client is lost forever.The only way to recover is to reconnect.
Provide version info
It's been there for a long time
Expected behavior
having information about currently running utPLSQL test / package is very valuable however it should be handled differently.
utPLSQL should grab information about application info before it starts and should recover that information when it finishes.
We could use events mechanism to trigger registration of application context and send it into application_context event handler so we could:
The text was updated successfully, but these errors were encountered: