> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# run (utPLSQL)

> Executes individual utPLSQL test packages using the run operation. utPLSQL version 2.3.1+ only. Target Properties Property Name Property Code Required

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

# Target Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>utPLSQL Database User</td><td>`FDUTPLSQL_DB_USER`</td><td>Yes</td><td>User used to connect to the associated database.</td></tr><tr><td>utPLSQL Database Password</td><td>`FDUTPLSQL_DB_PASSWORD`</td><td>Yes</td><td>Password for the utPLSQL Database User.</td></tr><tr><td>utPLSQL Database Connection Identifier</td><td>`FDUTPLSQL_DB_CONNECTION_IDENTIFIER`</td><td>Yes</td><td>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)))`" ).</td></tr><tr><td>utPLSQL Oracle Home Directory</td><td>`FDUTPLSQL_ORACLE_HOME`</td><td>Yes</td><td>Directory for Oracle Home (e.g. "`oracle/product/11.2.0/xe`"), used to run sqlplus.</td></tr></tbody></table>

# Inputs

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Input Name**</th><th>**Input Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Test Package In</td><td>`FDUTPLSQL_RUN_INP_TEST_PACKAGE_IN`</td><td>Yes</td><td>The name of the test package to run.\*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.</td></tr><tr><td>Autocompile On</td><td>`FDUTPLSQL_RUN_INP_AUTOCOMPILE_ON`</td><td>No</td><td>Pass `FALSE` to avoid auto-recompilation for the run operation. The default settings for utPLSQL is to re-compile your base package before each unit test.</td></tr><tr><td>Prefix In</td><td>`FDUTPLSQL_RUN_INP_PREFIX_IN`</td><td>No</td><td>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, `NULL` is used as a default. i.e. the package name is used as provided in the first parameter.</td></tr><tr><td>Suite In</td><td>`FDUTPLSQL_RUN_INP_SUITE_IN`</td><td>No</td><td>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.</td></tr><tr><td>Owner In</td><td>`FDUTPLSQL_RUN_INP_OWNER_IN`</td><td>No</td><td>The name of the schema that contains the packages to be tested.</td></tr><tr><td>Reset Results In</td><td>`FDUTPLSQL_RUN_INP_RESET_RESULTS_IN`</td><td>No</td><td>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.</td></tr><tr><td>From Suite In</td><td>`FDUTPLSQL_RUN_INP_FROM_SUITE_IN`</td><td>No</td><td>Pass `TRUE` to tell utPLSQL that this test is being run from within a test suite (for internal use only).</td></tr><tr><td>Subprogram In</td><td>`FDUTPLSQL_RUN_INP_SUBPROGRAM_IN`</td><td>No</td><td>Pass a string to restrict which of the test procedures will be executed for this run. Default of '`%`' means all tests will be run.</td></tr><tr><td>Per Method Setup In</td><td>`FDUTPLSQL_RUN_INP_PER_METHOD_SETUP_IN`</td><td>No</td><td>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.</td></tr></tbody></table>

# Artifacts

This operation doesn’t consume or produce any artifacts.

# Endpoint Selection

This operation will select all available endpoints associated to the Target.

# Endpoint Execution 

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

Executes individual utPLSQL test packages using the run operation.