Unit testing packages in sql developer

It appears that the specify parameters window is blank for packaged functions which means the test call fails when run. Is this a grant or synonym issue ( or something similar ) or is there an issue with testing packages via the unit test interface of sql developer. Thanks in advance.

Seems that you cannot right click on the packaged schema object from the schema connection i.e. you have to create the test from the unit test tab and then choose the object type i.e select packages and then the packaged function or procedure. This method results in the Specify Parameters window having the correct signature displayed. Procedures or methods can be created via the unit test tab or the active connection tab.

Similar Messages

ORA-01722 when opening a package in SQL Developer 1.2 with oracle 9iR1

Hi,
I use SQL Developer with Oracle Database 9i release 1.
When I open a package in SQL Developer 1.2 (or 1.5) for editing, I receive the error ORA-01722. The package successfully opens but this message, which pops everytime, is really annoying.
I monitored the requests sent by SQL Developer and it seems that the following request is responsible of the error :
SELECT LINE,POSITION,TEXT,ATTRIBUTE FROM USER_ERRORS WHERE TYPE=:1AND NAME=:2
Notice there are no spaces between ':1' and 'AND'. When executing 'by hand' the request with SQL Developer, it asks for the value of '1AND' bind variable and the value of '2'. Then, it fails to execute with... ORA-01722.
Is it possible to avoid this bug ?
Thank you for your help.

We're doing rolling 2 week releases until production. Expect something new next week.

How to debug package in sql developer?

Hi,
I need to debug one of procedures in my package in sql developer version 1.5.5. In Debugging log, I got the following:
Connecting to the database <databasename>.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '2754' )
ORA-01031: insufficient privileges
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
This session requires DEBUG CONNECT SESSION and DEBUG ANY PROCEDURE user privileges.
Process exited.
Disconnecting from the database <databasename>.
I have granted both DEBUG CONNECT SESSION and DEBUG ANY PROCEDURE user privileges from SYS as the following:
GRANT DEBUG ANY PROCEDURE TO ESM_OWNER;
grant DEBUG CONNECT SESSION to ESM_OWNER;
However, I still get the same error. What did I do wrong? I really appreciate any help to solve my problem.
Thanks in advance!!!
Cindy

I logged in as ESM_Owner. Now I got the following errors:
Connecting to the database <databasename>.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '1131' )
ORA-30683: failure establishing connection to debugger
ORA-12541: TNS:no listener
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database <databasename>.
Edited by: user13375135 on Sep 22, 2010 1:31 PM

Creating Data Mining PL/SQL Package in SQL Developer

hi,
i have built a model and want to create a PL/SQL package.
in SQL developer, i launch a "New Gallery", select "All Items" from the drop-down menu, and click on "Database Objects". but in the right window pane, i am not able to see "Data Mining PL/SQL Package" in the options.
can somebody please tell me how to fix this?
thanks!

To verify that Oracle Data Mining PL/SQL Package extension is properly installed, please do the following:
Select Menu Help->About, click on "Extensions" tab. Look for "Oracle Data Mining PL/SQL Package" in the Name column ( you can sort it).
If it is, please make a note of the version installed and post it here as well as the SQL Developer version.
Just to clarify, you don't see "Data Mining PL/SQL Package" item in the "Database Objects" at all or is it grayed out?
Thanks

Unit Testing in PL/SQL

Hi,
I m writing some packages and in that some procedures are there. Now i want to test these procedures. I have downloaded utPLSQL from sourceforge.net
But I am unable to use it. Do we need to copy those utPLSQL files where the orcale is present ? If so and after that do we need to run any .sql scripts before going to do Unit Testing.
And please tell the procedure in brief in order to start Unit Testing.
Thanks in Advance.

I suggest you also check out Quest Code Tester for Oracle (disclosure: I design, build and use the tool - hey, I also wrote the original version of utPLSQL!), the first commercial automated testing tool for PL/SQL.
www.quest.com/code-tester-for-oracle
It generates virtually all of your test code, based on expected behavior you describe through a point and click interface. You can run tests through the UI or scheduled scripts.
Regards,
Steven Feuerstein
www.ToadWorld.com/SF

BUG: Unit Testing Process Validations SQL editor - extra spaces appended

There is a bug in the SQL editor used by Unit Testing Process Validations.
To re-create:
Create a Validation with some multi-line SQL and save:
select *
from DUAL
where 1=1
Click on a different Validation, and then click back onto the Validation just created. SQL Developer will have appended a space to all the lines except the last one. Edit the Validation and save:
select *
from DUAL
where 1=2
When you navigate to a different validation and back, SQL Developer will have appended an extra space to each line. This can be repeated - each time an extra space will be added.

There is a bug in the SQL editor used by Unit Testing Process Validations.
To re-create:
Create a Validation with some multi-line SQL and save:
select *
from DUAL
where 1=1
Click on a different Validation, and then click back onto the Validation just created. SQL Developer will have appended a space to all the lines except the last one. Edit the Validation and save:
select *
from DUAL
where 1=2
When you navigate to a different validation and back, SQL Developer will have appended an extra space to each line. This can be repeated - each time an extra space will be added.

Creating PL/SQL package in SQL Developer 4.0.0.12

Hi,
I have built a model in SQL Developer 4.0.0.12 and I want to create it's PL/SQL package.
In ODMiner 11.1.0.4 from "Tools" > "Create pl/sql package" I can get a script for creating package and every thing is OK.
but in SQL Developer I select "Deploy" from every node's context menu and it generates a folder containing some scripts related to every node. I don't see any relevant script for creating any package.
How can I create relevant PL/SQL package from my workflow?
Thank you for any help you can provide in this situation.

Please refer to this White paper for how to generate PL/SQL package for workflow deployment:
Oracle Data Miner (Extension of SQL Developer 4.0)
Generate a PL/SQL script for workflow deployment
http://www.oracle.com/technetwork/database/options/advanced-analytics/odmrcodegenwhitepaper-2042206.pdf

Setting/using a variable in a package in SQL Developer

The 10g db I'm working with has a package that contains a variable and routines to set and get the value of the variable. The variable is used in a number of views to tailor data displayed according to the variable value. This all works well in applications, which set the variable after a connection is opened and then issue queries against the views, and then close the connection.
This also works well in Toad - I can open Toad, run a package routine to set the value and then open views (or run queries against views) in Toad to see how different variable values effect the data displayed. The package variable maintains its value so long as Toad is open, which seems to imply that Toad keeps a connection open.
But I can't use SQL Developer in the same way. I can run the SET routine, but it has no effect in on views subsequently run. When running the SET routine, setting the value to 1, the output is:
Connecting to the database HERC DB.
Process exited.
Disconnecting from the database HERC DB.
I can then run the GET routine, but the value of the variable is always zero:
Connecting to the database HERC DB.
v_Return = 0
Process exited.
Disconnecting from the database HERC DB.
The implication seems to be that a connection is made, the routine is run and then the connection is closed. The closing of the connection resets the variable. Is there some way I can have SQL Developer behave like Toad, such that the package variable value is maintained for my SQL Developer session? I've looked at connection roperties and application preferences, but I've not seen anything that seems to be related keeping a connection open.
BTW, I have tried the "connection startup script", but to no avail. Perhaps I've doen this improperly; the script simply attempts to invoke the package set routine, like so: myPkg.set_identity(1)
Thanks.
Edited by: user483973 on Oct 20, 2009 9:20 AM

When running stored PL/SQL through the IDE context node or editor, indeed a new session is opened and consequently closed on completion after committing. Although great for having the IDE free to continue working, it does have its drawbacks when you want variables to persist and changes to be visible in the IDE before committing.
To prevent the new session and the commit, just call the PL/SQL from a worksheet (in a call, query or anonymous block).
The startup script should work in that respect, but make sure to wrap your call in an anonymous block, else you'll get a syntax error.
Hope that helps,
K.

Issue with viewing packages in SQL Developer EA2

I posted a message when EA1 came out asking why I couldn't see the package's body in EA1.
Now I couldn't see the any thing under '$schema/packages' in EA2.
Does anybody know why?
My OS: Windows XP Pro SP2
Oracle: 9i
SQL Developer version: EA2

In version 9 a very simple sql is supposed to be executed:
SELECT OBJECT_NAME, OBJECT_ID,
DECODE(STATUS, 'INVALID', 'TRUE', 'FALSE') INVALID,
'TRUE' runnable
FROM SYS.ALL_OBJECTS a
WHERE OWNER = :SCHEMA
AND OBJECT_TYPE = 'PACKAGE'
AND SUBOBJECT_NAME IS NULL
-- for packages
SELECT OBJECT_NAME, OBJECT_ID,
DECODE(STATUS, 'INVALID', 'TRUE', 'FALSE') INVALID,
'TRUE' runnable
FROM SYS.ALL_OBJECTS o
WHERE OWNER =:SCHEMA
AND OBJECT_NAME = :PARENT_NAME
AND OBJECT_TYPE = 'PACKAGE BODY'
-- for package bodies
If either of these doesn't return anything in worksheet, then the problem is right there. However, this part hasn't been changed since EA1 (The only change was adding SYS.DBA_PLSQL_OBJECT_SETTINGS requirement for version >=10). I can't reproduce the problem: in 9i scott sees any procedure/package I create.

Privileges to view packages in Sql Developer

I'm sure this has been covered before, but I cannot view a package (spec or body) unless Execute has been granted.
Create any procedure will allow spec/body to be displayed.
Is this as intended?
I searched the forum and elsewhere, and found comments and workarounds. What I am looking for is the actual rules that determine when a package can be viewed.

You could probably connect to the database with toad, have the session traced, and click around and view some packages to see what sql was run, then do the same with sql developer. My guess would be the views that each tool is using by default, perhaps toad goes ofter dba_objects/source and maybe sql developer goes after all_objects/source, something like that. so with a permission like select any view or select any table, you might see different results depending on the tool, Purely speculation on my part.

Very new to this: Cannot see code for a package in SQL Developer

I know I'm doing something wrong but I certainly don't know what. I'm looking for the code to go along with a package. I can see the procedures the package calls and I can see a list of procedures but I cannot see the code for those procedures. I have tried using describe on the pop up and I just don't see anything but a window showing me the parameters the procedure will use. I want to see the code it will use.
Can someone walk me through this or point me in the right direction?
TIA

I can only assume you're on 2.1 or 2.1.1 since you don't even say. If you click on the tree showing the various objects after establishing your connection, when you get to packages and you click the package you want, you'll see the spec. Now click on the plus sign and there should be 'package name' body. If you click that body icon, you say you still can't see the code?
Evita
Edited by: Evita on Mar 30, 2010 2:59 PM

Create Unit Test wizard does not populate parameters

If I right click a standalone function or procedure and select "Create Unit Test", the parameters window is populated and I am able to enter input and expected output values for the test.
However, when I attempt the same with a function that is within a package, the parameters window is blank.
I am using version 3.2.20.09

Looks like someone has already reported this bug (and a workaround) in this thread:
unit testing packages in sql developer
Edited by: AJMiller on Dec 11, 2012 9:24 AM

Unit Test exports between different SQL Developer versions

Hi,
I am having problems with trying to export and import unit test suites between SQL Developer versions. I can't find any documentation in this area. We have a number of unit test suites exported as XML files from version 2.1.1.64, and below are combinations of things I have tried:
- I have tried to import a unit test suite into version 3.0.0.4 that was exported from version 2.1.1.64 and get the error "Import failed. unexpected null value". I expect that this is probably an unsupported action due to repository changes between the two versions - should I be able to do this?
- I have upgraded the repository with unit tests in it. The unit tests run perfectly well in the upgraded repository. However, if I try to export any suites or individual tests, I get an error "Export failed.". A XML file is created but with what looks like only the header part of it.
- I have created a new unit test suite in version 3.0.0.4 and this exports successfully.
- I have gone into each test of a suite in the upgraded repository and made a change so that I can perform a commit. When I do an export, this does then work successfully.
Therefore it appears that something is not carried out by default when the repository is upgraded, but this fixes itself if the test is amended and committed in the upgraded repository. Although this may be a workaround, we have 100's of tests and is not something I really want to do. Has anyone else experienced this and got any recommendations for this?
Thanks, Pierre.

Hi,
I am having problems with trying to export and import unit test suites between SQL Developer versions. I can't find any documentation in this area. We have a number of unit test suites exported as XML files from version 2.1.1.64, and below are combinations of things I have tried:
- I have tried to import a unit test suite into version 3.0.0.4 that was exported from version 2.1.1.64 and get the error "Import failed. unexpected null value". I expect that this is probably an unsupported action due to repository changes between the two versions - should I be able to do this?
- I have upgraded the repository with unit tests in it. The unit tests run perfectly well in the upgraded repository. However, if I try to export any suites or individual tests, I get an error "Export failed.". A XML file is created but with what looks like only the header part of it.
- I have created a new unit test suite in version 3.0.0.4 and this exports successfully.
- I have gone into each test of a suite in the upgraded repository and made a change so that I can perform a commit. When I do an export, this does then work successfully.
Therefore it appears that something is not carried out by default when the repository is upgraded, but this fixes itself if the test is amended and committed in the upgraded repository. Although this may be a workaround, we have 100's of tests and is not something I really want to do. Has anyone else experienced this and got any recommendations for this?
Thanks, Pierre.

SQL Developer Unit Test

I'm trying out the Unit Test tool in SQL Developer version 3.2.09 and I keep getting the following error on the Teardown Process:
Teardown Table or Row Restore (1/1) failed: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 22
I have no idea what line 22 refers to? I cannot seem to find more detailed information in order to correct the problem.
Any insight or help would be great!
Thanks,
Paul

I'm having the same issue with SQL Developer 3.2.20.09 on Oracle 11.2.0.3.0. However, I think it's somewhat data dependent as I've had success and I've also encountered the ORA-06502 error.
I ran a generic test on a very simple table and was successful using the teardown restore of the table. The procedure isn't important in this scenario, but is given as reference to creating the test. The simple, successful case is given first.
Note that in both cases/tests, the original table of data already existed, so I question the error message pointing to data being inserted is longer than the field allows or that data types are somehow different...+unless+ SQL Developer is translating or getting it wrong. ALSO NOTE, running the SQL inserts as given works if run through the worksheet. It's only in the Teardown that I see the ORA-06502 error message.
Data
CREATE TABLE EMPLOYEES (EMPLOYEE_ID NUMBER, COMMISSION_PCT NUMBER, SALARY NUMBER);
Insert into EMPLOYEES (EMPLOYEE_ID,COMMISSION_PCT,SALARY) values (1001,0.2,8400);
Insert into EMPLOYEES (EMPLOYEE_ID,COMMISSION_PCT,SALARY) values (1002,0.25,6000);
Insert into EMPLOYEES (EMPLOYEE_ID,COMMISSION_PCT,SALARY) values (1003,0.3,5000);
CREATE OR REPLACE PROCEDURE AWARD_BONUS AS
BEGIN
null;
END award_bonus;
Startup: Table or Row Copy
description = "TMP$AWARD_BONUS_TEST" := SELECT ROWID AS SRC$ROWID, s.* FROM "EMPLOYEES" s
source = "EMPLOYEES"
temp = "TMP$AWARD_BONUS_TEST"
Teardown: Table or Row Restore
description = "TMP$AWARD_BONUS_TEST" -> "EMPLOYEES"
source = "EMPLOYEES"
key = PRIMARY KEY
temp = "TMP$AWARD_BONUS_TEST"
The above worked without error.
The following did not work.* (Again, the procedure isn't relevant.)
Data
CREATE TABLE "xxdss_fact_detail_history"
"fact_trx_id" NUMBER(15, 0),"number_of_records" NUMBER,
"product_code" VARCHAR2(250 byte),"item_code" VARCHAR2(250 byte),
"item_description" VARCHAR2(250 byte),"trade" VARCHAR2(250 byte),
"item_system" VARCHAR2(250 byte),"unit" VARCHAR2(250 byte),
"fuel_source" VARCHAR2(250 byte),"component" VARCHAR2(250 byte),
"assembly" VARCHAR2(250 byte),"part" VARCHAR2(250 byte),
"symptoms" VARCHAR2(250 byte),"diagnosis_item" VARCHAR2(250 byte),"coa"
VARCHAR2(250 byte),"cchs_parts" VARCHAR2(250 byte),
"region" VARCHAR2(250 byte),"state" VARCHAR2(250 byte),
"county" VARCHAR2(250 byte),"zip" VARCHAR2(250 byte),"vendor_id" NUMBER,
"vendor_site_id" NUMBER,"vendor_name" VARCHAR2(250 byte),
"vendor_site" VARCHAR2(250 byte),"c_service_call_cost" NUMBER,
"c_labor_cost" NUMBER,"c_part_cost" NUMBER,"c_tax" NUMBER,
"c_cchs_oh_cost" NUMBER,"c_cchs_total_low_cost" NUMBER,
"c_cchs_total_high_cost" NUMBER,"c_cchs_avg_total_cost" NUMBER,
"c_nc_c_labor_cost" NUMBER,"c_nc_c_part_cost" NUMBER,"c_nc_tax_cost" NUMBER
,"c_nc_total_low_cost" NUMBER,"c_nc_total_high_cost" NUMBER,
"c_nc_avg_total_cost" NUMBER,"c_flat_low_cost" NUMBER,
"c_flat_high_cost" NUMBER,"c_flat_avg_cost" NUMBER,
"p_cycle_time_day_low" NUMBER,"p_cycle_time_day_high" NUMBER,
"p_cycle_avg_time_day" NUMBER,"p_reasgn_low" NUMBER,"p_reasgn_high" NUMBER,
"p_reasgn_avg" NUMBER,"p_recall_low" NUMBER,"p_recall_high" NUMBER,
"p_recall_avg" NUMBER,"s_sp_nps_score_low" NUMBER,
"s_sp_nps_score_high" NUMBER,"s_sp_avg_nps_score" NUMBER,
"s_cchs_nps_score_low" NUMBER,"s_cchs_nps_score_high" NUMBER,
"s_cchs_avg_nps_score" NUMBER,"cps_cost" NUMBER,"cps_perfrmce" NUMBER,
"cps_sat" NUMBER,"coa_score" NUMBER,"comments" VARCHAR2(4000 byte),
"complete_flag" VARCHAR2(1 byte),"last_update_date" DATE,
"last_updated_by" NUMBER(15, 0),"creation_date" DATE,
"created_by" NUMBER(15, 0),"last_update_login" NUMBER(15, 0),
"vendor_number" VARCHAR2(200 byte)
SET DEFINE OFF;
Insert into XXDSS.XXDSS_FACT_DETAIL_HISTORY (FACT_TRX_ID,NUMBER_OF_RECORDS,PRODUCT_CODE,ITEM_CODE,ITEM_DESCRIPTION,TRADE,ITEM_SYSTEM,UNIT,FUEL_SOURCE,COMPONENT,ASSEMBLY,PART,SYMPTOMS,DIAGNOSIS_ITEM,COA,CCHS_PARTS,REGION,STATE,COUNTY,ZIP,VENDOR_ID,VENDOR_SITE_ID,VENDOR_NAME,VENDOR_SITE,C_SERVICE_CALL_COST,C_LABOR_COST,C_PART_COST,C_TAX,C_CCHS_OH_COST,C_CCHS_TOTAL_LOW_COST,C_CCHS_TOTAL_HIGH_COST,C_CCHS_AVG_TOTAL_COST,C_NC_C_LABOR_COST,C_NC_C_PART_COST,C_NC_TAX_COST,C_NC_TOTAL_LOW_COST,C_NC_TOTAL_HIGH_COST,C_NC_AVG_TOTAL_COST,C_FLAT_LOW_COST,C_FLAT_HIGH_COST,C_FLAT_AVG_COST,P_CYCLE_TIME_DAY_LOW,P_CYCLE_TIME_DAY_HIGH,P_CYCLE_AVG_TIME_DAY,P_REASGN_LOW,P_REASGN_HIGH,P_REASGN_AVG,P_RECALL_LOW,P_RECALL_HIGH,P_RECALL_AVG,S_SP_NPS_SCORE_LOW,S_SP_NPS_SCORE_HIGH,S_SP_AVG_NPS_SCORE,S_CCHS_NPS_SCORE_LOW,S_CCHS_NPS_SCORE_HIGH,S_CCHS_AVG_NPS_SCORE,CPS_COST,CPS_PERFRMCE,CPS_SAT,COA_SCORE,COMMENTS,COMPLETE_FLAG,LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATION_DATE,CREATED_BY,LAST_UPDATE_LOGIN,VENDOR_NUMBER) values (324,2,'L&F-MPP03TR','STCOL-SPL','Straight Cool Split System','HVAC',null,'STCOL-SPL',null,null,null,null,null,null,'REAPIR','N',null,'VA','ASHBURN','20148',22024,118957,'Air Lingus Inc',null,50,55,44,12,180,40,78,76.5,60,50,20,100,180,130,50,110,80,2,8,3.9323148148178,40,60,43,9,10,8.2,100,201,150,20,40,35,50,30,20,100,null,null,to_date('01-JAN-13','DD-MON-RR'),1,to_date('01-JAN-13','DD-MON-RR'),1,null,'122023');
Insert into XXDSS.XXDSS_FACT_DETAIL_HISTORY (FACT_TRX_ID,NUMBER_OF_RECORDS,PRODUCT_CODE,ITEM_CODE,ITEM_DESCRIPTION,TRADE,ITEM_SYSTEM,UNIT,FUEL_SOURCE,COMPONENT,ASSEMBLY,PART,SYMPTOMS,DIAGNOSIS_ITEM,COA,CCHS_PARTS,REGION,STATE,COUNTY,ZIP,VENDOR_ID,VENDOR_SITE_ID,VENDOR_NAME,VENDOR_SITE,C_SERVICE_CALL_COST,C_LABOR_COST,C_PART_COST,C_TAX,C_CCHS_OH_COST,C_CCHS_TOTAL_LOW_COST,C_CCHS_TOTAL_HIGH_COST,C_CCHS_AVG_TOTAL_COST,C_NC_C_LABOR_COST,C_NC_C_PART_COST,C_NC_TAX_COST,C_NC_TOTAL_LOW_COST,C_NC_TOTAL_HIGH_COST,C_NC_AVG_TOTAL_COST,C_FLAT_LOW_COST,C_FLAT_HIGH_COST,C_FLAT_AVG_COST,P_CYCLE_TIME_DAY_LOW,P_CYCLE_TIME_DAY_HIGH,P_CYCLE_AVG_TIME_DAY,P_REASGN_LOW,P_REASGN_HIGH,P_REASGN_AVG,P_RECALL_LOW,P_RECALL_HIGH,P_RECALL_AVG,S_SP_NPS_SCORE_LOW,S_SP_NPS_SCORE_HIGH,S_SP_AVG_NPS_SCORE,S_CCHS_NPS_SCORE_LOW,S_CCHS_NPS_SCORE_HIGH,S_CCHS_AVG_NPS_SCORE,CPS_COST,CPS_PERFRMCE,CPS_SAT,COA_SCORE,COMMENTS,COMPLETE_FLAG,LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATION_DATE,CREATED_BY,LAST_UPDATE_LOGIN,VENDOR_NUMBER) values (465,4,'L&F-MPP03TR','STCOL-SPL','Straight Cool Split System','HVAC',null,'STCOL-SPL',null,null,null,null,null,null,'REPLACE','N',null,'VA','ASHBURN','20148',1768,1090523,'Airmax Heating And Air Conditioning Llc',null,65,50,80,15,110,50,60,70,70,40,20,100,180,130,50,110,80,3,5,0.878969907411374,10,70,20,1,2,2,130,150,140,20,40,60,40,30,30,100,null,null,to_date('01-JAN-13','DD-MON-RR'),1,to_date('01-JAN-13','DD-MON-RR'),1,null,'101767');
CREATE OR REPLACE PROCEDURE dss AS
BEGIN
null;
END dss;
Startup: Table or Row Copy
description = "TMP$DSS_TEST" := SELECT ROWID AS SRC$ROWID, s.* FROM "XXDSS_FACT_DETAIL_HISTORY" s
source = "XXDSS_FACT_DETAIL_HISTORY"
temp = "TMP$DSS_TEST"
Teardown: Table or Row Restore
description = "TMP$DSS_TEST" -> "XXDSS_FACT_DETAIL_HISTORY"
source = "XXDSS_FACT_DETAIL_HISTORY"
key = PRIMARY KEY
temp = "TMP$DSS_TEST"

Unit Test Variable Substitution in PL/SQL User Vailidation code not running

Hi
I am using new Unit Test Feature in SQL Developer 2.1.0.62.
I have created a test implemented to test a function. The function has a VARCHAR2 parameter as input and returns a BINARY_INTEGER.
I would like to perform 'Process Validation instead of specifying an explicit 'Result'. The check box 'Test Result' is unchecked.
I have seen in the doc. that I can use substitution variables in my user defined PL/SQL code. I try
IF {RETURNS$} < 0
THEN ...
but I always get the error
ERROR
<RETURN> : Expected: [Any value because apply check was cleared], Received: [-103]
Validation User PL/Sql Code failed: Non supported SQL92 token at position: 181: RETURNS$
Obviously, the program doesn't recognize {RETURN$}.
Am I missing something?
br
Reiner

Hi all,
I have installed the latest version of SQL Developer (2.1.1) that fixed the problem - must have been a bug.
The only problem was that I got an ORA-904 TEST_USER_NAME... error. I export my tests, dropped the repository, created a new one and reimported everything. Now it works as it should.
br
Reiner

Unit testing packages in sql developer

Similar Messages

Maybe you are looking for