Page Comparison

Executes utPLSQL v3 test cases using ut.run(options). utPLSQL version 3.0+ only.

...

Input Name

Input Code

Required

Description

Suite Path

FDUTPLSQL_INP_RUN_PATH

No

@before 5.6.0.1 Input name was called "Run Path" and was required.

A suite path or a comma separated list of suite paths for unit test to be executed. This can be a schema, package, procedure, function, etc... If only schema is provided, then all suites owned by that schema are executed. If not set, then the current schema is used. IE: 'hr' or 'hr:com.my_org.my_project' or 'hr.test_apply_bonus,customers'

Reporters

FDUTPLSQL_INP_REPORTERS

No

@since 5.6.0.1

Select output reporting format(s). UT_JUNIT_REPORTER is always added, therefore, is not in the list. For each reporter selected the corresponding file will be exported to the reports tab on the project workflow execution.

Available reporters include: UT_COVERAGE_COBERTURA_REPORTER, UT_COVERAGE_HTML_REPORTER, UT_COVERAGE_SONAR_REPORTER, UT_COVERALLS_REPORTER, UT_DEBUG_REPORTER, UT_DOCUMENTATION_REPORTER, UT_REALTIME_REPORTER, UT_SONAR_TEST_REPORTER, UT_TEAMCITY_REPORTER, UT_TFS_JUNIT_REPORTER

Read more about the different reporter types.

Tags

FDUTPLSQL_INP_TAGS

No

@since 5.6.0.1

A comma separated list of tags to run. IE: 'suite1' or 'suite1,suite2' or '-suite1'. Filtering the tests to be run is in addition to any suite paths paths defined. The framework applies OR logic to all specified tags so any test / suite that matches at least one tag will be included in the test run. You can also exclude specific tags by adding a - (dash) in front of the tag.

Coverage Schemes

FDUTPLSQL_INP_COVERAGE_SCHEMES

No

@since 5.6.0.1

A comma separated list of schemas on which coverage should be gathered. Only applicable to coverage reporters.

Fail on Errors

FDUTPLSQL_INP_FAIL_ON_ERRORS

No

@since 5.6.0.1

Force workflow execution to fail if UTPLSQL run fails any tests. When set to false UTPLSQL run always exits with a success status. Defaults to false.

Skip Compatibility Check

FDUTPLSQL_INP_SKIP_COMPATIBILITY_CHECK

No

@since 5.6.0.1

Skips the compatibility check with the version of the database framework. If you skip compatibility check, CLI will expect the most latest framework version.

Random Test Order

FDUTPLSQL_INP_RANDOM_TEST_ORDER

No

@since 5.6.0.1

Enables random order of test executions.

Random Test Order Seed

FDUTPLSQL_INP_RANDOM_TEST_ORDER_SEED

No

@since 5.6.0.1

Sets the seed to use for random test execution order. If set, Random Test Order is set to true.

Include Objects

FDUTPLSQL_INP_INCLUDE_OBJECTS

No

@since 5.6.0.1

Comma-separated object list to include in the coverage report. Only applicable to coverage reporters.

Exclude Objects

FDUTPLSQL_INP_EXCLUDE_OBJECTS

No

@since 5.6.0.1

Comma-separated object list to exclude in the coverage report. Only applicable to coverage reporters.

Source File Mapping

FDUTPLSQL_INP_SOURCE_FILE_MAPPING_JSON

No

@since 5.6.0.1

JSON for path to project source files with options to enable custom type mappings. Map database object names to project files. Keys must be spelled as shown in the example below and "file_paths" is the only required JSON field.

Code Block

language	text
theme	Eclipse
title	JSON Example
linenumbers	true
collapse	true

{ 
    "file_paths": [{"path": "sources"}],
    "type_mapping": [{"key": "packages_bodies", "value": "PACKAGE BODY"}, {"key": "types_bodies", "value": "TYPE BODY"}],
    "owner": "code_owner",
    "regex_expression": "((\w+)/)?(\w+)\.(\w{3})$",
	"owner_subexpression": 2,
    "name_subexpression": 3,
    "type_subexpression": 4
}

Read more about custom type mappings under the Project based Coverage section.

Test File Mapping

FDUTPLSQL_INP_TEST_FILE_MAPPING_JSON

No

@since 5.6.0.1

JSON for path to project test files with options to enable custom type mappings. Map database object names to test files. Keys must be spelled as shown in the example below and "file_paths" is the only required JSON field.

Code Block

language	text
theme	Eclipse
title	JSON Example
linenumbers	true
collapse	true

{ 
    "file_paths": [{"path": "hr"}, {"path": "customers"}],
    "type_mapping": [{"key": "functions", "value": "FUNCTION"}, {"key": "triggers", "value": "TRIGGER"}],
    "owner": "tests_owner",
    "regex_expression": "(\w+)/(\w+)(\w+)\..{3}$",
	"owner_subexpression": 2,
    "name_subexpression": 3,
    "type_subexpression": 4
}

Read more about custom type mappings under the Project based Coverage section.

...

Versions Compared

Old Version 7

New Version Current

Key