Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Executes individual utPLSQL test packages using the test operation.  utPLSQL version 2.3.1+ only.

Target Properties

Property Name

Property Code

Required

Description

utPLSQL Database User

FDUTPLSQL_DB_USER

Yes

User used to connect to the associated database.

utPLSQL Database Password

FDUTPLSQL_DB_PASSWORD

Yes

Password for the utPLSQL Database User.

utPLSQL Database Connection Identifier

FDUTPLSQL_DB_CONNECTION_IDENTIFIER

Yes

Identifier used to connect to the Database for utPLSQL testing. Simply the SID can be used if the database is on the same server as the endpoint (e.g. "xe" ). If connecting to a server remotely from the endpoint server, the identifier will need to follow the remote connection syntax (e.g. "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(Host=localhost)(Port=1521))(CONNECT_DATA=(SID=xe)))" ).

utPLSQL Oracle Home Directory

FDUTPLSQL_ORACLE_HOME

Yes

Directory for Oracle Home (e.g. "oracle/product/11.2.0/xe"), used to run sqlplus.

Inputs

Input Name

Input Code

Required

Description

Package In

FDUTPLSQL_TEST_INP_PACKAGE_IN

Yes

The name of the package or stand-alone program to be tested.

*If utPLSQL Database User is not the test package owner, do not schema-qualify the package. Instead, place the schema name in the Owner In parameter.

Recompile In

FDUTPLSQL_TEST_INP_RECOMPILE_IN

No

Pass FALSE if you do not want utPLSQL to automatically recompile your test package before running the test.

Same Package In

FDUTPLSQL_TEST_INP_SAMEPACKAGE_IN

No

Pass TRUE if your unit test programs are defined in the same package as the source code to be tested. The default is that you have created a separate package.

Prefix In

FDUTPLSQL_TEST_INP_PREFIX_IN

No

The prefix to be appended to package_in to come up with the name of the test package. If you do not provide a value, the last prefix you specified (or the default) will be used.

Directory In

FDUTPLSQL_TEST_INP_DIR_IN

No

The directory containing the test package source code. If you do not provide a value in your call to utPLSQL.test (the default) and if you have not turned off automatic recompilation, utPLSQL will look for the test package source code in the directory specified by a call to utConfig.setdir. If you do not provide a value, the last directory youspecified (if any) will be used.

Suite In

FDUTPLSQL_TEST_INP_SUITE_IN

No

The name of the suite that contains the specified test package. This is an optional value and is used to update statistics for the test.

Owner In

FDUTPLSQL_TEST_INP_OWNER_IN

No

The name of the schema that

was specified when the test suite was defined and the packaged added to the suite. This is an optional value and is used to update statistics for the test.

contains the packages to be tested.

Reset Results In

FDUTPLSQL_TEST_INP_RESET_RESULTS_IN

No

Pass FALSE to tell utPLSQL to not reset the results information, in which case you will still be able to view results by calling utResult.show . Otherwise, utPLSQL clears the result data after each test.

From Suite In

FDUTPLSQL_TEST_INP_FROM_SUITE_IN

No

Pass TRUE to tell utPLSQL that this test is being run from within a test suite (for internal use only).

Subprogram In

FDUTPLSQL_TEST_INP_SUBPROGRAM_IN

No

Pass a string to restrict which of the test procedures will be executed for this run. Default of '%' means all tests will be run.

Per Method Setup In

FDUTPLSQL_TEST_INP_PER_METHOD_SETUP_IN

No

Pass TRUE to run the setup and teardown procedure before and after each unit test procedure is executed. Default of FALSE means that these programs will be run once, at the start and end of the package test execution as a whole.

Override Package In

FDUTPLSQL_TEST_INP_OVERRIDE_PACKAGE_IN

No

Override the automatic determination of package names thus removing the one to one relationship between test package and package to test. Default is NULL. Instead of using this parameter consider using the

procedure

run operation.

Artifacts

This operation delegates the doesn’t consume /or produce any artifacts decision to the workflow developer.

Endpoint Selection

This operation delegates the selection will select all available endpoints associated to the workflow developer to determineTarget.

Endpoint Execution

This operations delegates the execution to the workflow developer to decideoperation will execute on any one of the selected endpoints and will be random in the determination of which one.