Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Executes utPLSQL test suites using the runSuite operation.

Environment/Instance Properties

Property Name

Property Code

Required

Description

utPLSQL Database UserFDUTPLSQL_DB_USER

Yes

User used to connect to the associated database.
utPLSQL Database PasswordFDUTPLSQL_DB_PASSWORDYesPassword for the utPLSQL Database User.
utPLSQL Database Connection IdentifierFDUTPLSQL_DB_CONNECTION_IDENTIFIERYesIdentifier 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 DirectoryFDUTPLSQL_ORACLE_HOMEYesDirectory for Oracle Home (e.g. "oracle/product/11.2.0/xe"), used to run sqlplus.

Inputs

Input Name

Input Code

Required

Description

Suite InFDUTPLSQL_RSUITE_INP_SUITE_INYesThe name of the test suite to run.
Autocompile OnFDUTPLSQL_RSUITE_INP_AUTOCOMPILE_ON
NoPass FALSE to avoid auto-recompilation for the runSuite operation. The default settings for utPLSQL is to re-compile your base package before each unit test.
Reset Results InFDUTPLSQL_RSUITE_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.

Per Method Setup InFDUTPLSQL_RSUITE_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 test suite execution as a whole.

Artifacts

This operation doesn’t consume or produce any artifacts.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance.

Endpoint Execution 

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

  • No labels