-
Notifications
You must be signed in to change notification settings - Fork 17
Run utPLSQL test greyed out in Schema Browser (other schema and own schema) #111
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
Comments
In the following scenario I'm connected to The statement log shows the code executed behind the scenes to determine if a package can be executed. The code may differ depending on the installed utPLSQL version (that's why it is important to know which version of utPLSQL you are using). In my case I use the most recent develop version v3.1.11.3466-develop). The code looks like this when showing the cell value of the DECLARE
l_return VARCHAR2(1) := '0';
BEGIN
IF ut_runner.is_suite(?, ?) THEN
l_return := '1';
END IF;
? := l_return;
END; The bind variables SET SERVEROUTPUT ON
DECLARE
l_return VARCHAR2(1) := '0';
BEGIN
IF ut_runner.is_suite('UT3_TESTER', 'TEST_OUTPUT_BUFFER') THEN
l_return := '1';
END IF;
dbms_output.put_line(l_return);
END;
/ In my chase the output is:
So, I assume that in your case |
Hi Philipp, We are using utPLSQL version v3.1.9.3270. I executed your piece of PL/SQL code and it returned 1 in my case, so this looks ok. However, I have found something else based on your feedback. Thanks, |
Thanks, good to know it's a bug and not something related to my configuration ;-) |
(oops maybe I should better not close this one) |
Thanks, I can confirm it's working fine now (I tried v1.2.1 with SQL Developer 20.2). |
Hi,
I'm using the utPLSQL extension version 1.2.0 with SQL Developer 19.4.
I can right-click in the connections window and run utPLSQL tests on packages in my own schema, but I cannot do this on packages in another schema - the utPLSQL options are greyed out. Any idea what could be causing this? If I run them like this from my own schema, it works fine:
set serveroutput on
begin
ut.run('other_schema.ut_package');
end;
PS: I have enough rights to create and execute objects in the other schema.
Thanks
Matthias
The text was updated successfully, but these errors were encountered: