You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+47-46Lines changed: 47 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,67 +6,68 @@ Provides an easy way of invoking utPLSQL from command-line. Main features:
6
6
* Ability to run tests with multiple reporters simultaneously.
7
7
* Ability to save output from every individual reporter to a separate output file.
8
8
* Allows execution of selected suites, subset of suite.
9
-
*~~Maps project and test files to database objects for reporting purposes.~~ (Comming Soon)
9
+
* Maps project and test files to database objects for reporting purposes. (Comming Soon)
10
10
11
11
## Downloading
12
12
You can download development versions on [Bintray](https://bintray.com/viniciusam/utPLSQL-cli/utPLSQL-cli-develop#files).
13
13
14
14
15
15
## Requirements
16
16
*[Java SE Runtime Environment 8](http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html)
17
-
*~~When using reporters for Sonar or Coveralls client needs to be invoked from project's root directory.~~
17
+
* When using reporters for Sonar or Coveralls client needs to be invoked from project's root directory.
18
18
19
19
## Usage
20
20
utplsql run user/pass@[[host][:port]/]db [-p=(ut_path|ut_paths)][-f=format [-o=output_file][-s] ...]
21
21
22
22
```
23
-
user - Username to connect as.
24
-
password - Password of the user.
25
-
host - Server address, defaults to 127.0.0.1.
26
-
port - Server port, defaults to 1521.
27
-
db - Database to connect to.
28
-
-p=suite_path(s) - A suite path or a comma separated list of suite paths for unit test to be executed.
29
-
The path(s) can be in one of the following formats:
30
-
schema[.package[.procedure]]
31
-
schema:suite[.suite[.suite][...]][.procedure]
32
-
Both formats can be mixed in the list.
33
-
If only schema is provided, then all suites owner by that schema are executed.
34
-
If -p is omitted, the current schema is used.
35
-
-f=format - A reporter to be used for reporting.
36
-
If no -f option is provided, the default ut_documentation_reporter is used.
37
-
Available options:
38
-
-f=ut_documentation_reporter
39
-
A textual pretty-print of unit test results (usually use for console output)
40
-
-f=ut_teamcity_reporter
41
-
For reporting live progress of test execution with Teamcity CI.
42
-
-f=ut_xunit_reporter
43
-
Used for reporting test results with CI servers like Jenkins/Hudson/Teamcity.
44
-
-f=ut_coverage_html_reporter
45
-
Generates a HTML coverage report with summary and line by line information on code coverage.
46
-
Based on open-source simplecov-html coverage reporter for Ruby.
47
-
Includes source code in the report.
48
-
-f=ut_coveralls_reporter
49
-
Generates a JSON coverage report providing information on code coverage with line numbers.
50
-
Designed for [Coveralls](https://coveralls.io/).
51
-
-f=ut_coverage_sonar_reporter
52
-
Generates a JSON coverage report providing information on code coverage with line numbers.
53
-
Designed for [SonarQube](https://about.sonarqube.com/) to report coverage.
54
-
-f=ut_sonar_test_reporter
55
-
Generates a JSON report providing detailed information on test execution.
56
-
Designed for [SonarQube](https://about.sonarqube.com/) to report test execution.
57
-
58
-
-o=output - Defines file name to save the output from the specified reporter.
59
-
If defined, the output is not displayed on screen by default. This can be changed with the -s parameter.
60
-
If not defined, then output will be displayed on screen, even if the parameter -s is not specified.
61
-
If more than one -o parameter is specified for one -f parameter, the last one is taken into consideration.
62
-
-s - Forces putting output to to screen for a given -f parameter.
63
-
-c - If specified, enables printing of test results in colors as defined by ANSICONSOLE standards.
64
-
Works only on reporeters that support colors (ut_documentation_reporter).
23
+
user - Username to connect as.
24
+
password - Password of the user.
25
+
host - Server address, defaults to 127.0.0.1.
26
+
port - Server port, defaults to 1521.
27
+
db - Database to connect to.
28
+
-p=suite_path(s) - A suite path or a comma separated list of suite paths for unit test to be executed.
29
+
The path(s) can be in one of the following formats:
30
+
schema[.package[.procedure]]
31
+
schema:suite[.suite[.suite][...]][.procedure]
32
+
Both formats can be mixed in the list.
33
+
If only schema is provided, then all suites owner by that schema are executed.
34
+
If -p is omitted, the current schema is used.
35
+
-f=format - A reporter to be used for reporting.
36
+
If no -f option is provided, the default ut_documentation_reporter is used.
37
+
Available options:
38
+
-f=ut_documentation_reporter
39
+
A textual pretty-print of unit test results (usually use for console output)
40
+
-f=ut_teamcity_reporter
41
+
For reporting live progress of test execution with Teamcity CI.
42
+
-f=ut_xunit_reporter
43
+
Used for reporting test results with CI servers like Jenkins/Hudson/Teamcity.
44
+
-f=ut_coverage_html_reporter
45
+
Generates a HTML coverage report with summary and line by line information on code coverage.
46
+
Based on open-source simplecov-html coverage reporter for Ruby.
47
+
Includes source code in the report.
48
+
-f=ut_coveralls_reporter
49
+
Generates a JSON coverage report providing information on code coverage with line numbers.
50
+
Designed for [Coveralls](https://coveralls.io/).
51
+
-f=ut_coverage_sonar_reporter
52
+
Generates a JSON coverage report providing information on code coverage with line numbers.
53
+
Designed for [SonarQube](https://about.sonarqube.com/) to report coverage.
54
+
-f=ut_sonar_test_reporter
55
+
Generates a JSON report providing detailed information on test execution.
56
+
Designed for [SonarQube](https://about.sonarqube.com/) to report test execution.
57
+
58
+
-o=output - Defines file name to save the output from the specified reporter.
59
+
If defined, the output is not displayed on screen by default. This can be changed with the -s parameter.
60
+
If not defined, then output will be displayed on screen, even if the parameter -s is not specified.
61
+
If more than one -o parameter is specified for one -f parameter, the last one is taken into consideration.
62
+
-s - Forces putting output to to screen for a given -f parameter.
63
+
-c - If specified, enables printing of test results in colors as defined by ANSICONSOLE standards.
64
+
Works only on reporeters that support colors (ut_documentation_reporter).
65
+
--failure-exit-code - Override the exit code on failure, defaults to 1. You can set it to 0 to always exit with a success status.
65
66
```
66
67
67
68
Parameters -f, -o, -s are correlated. That is parameters -o and -s are controlling outputs for reporter specified by the preceding -f parameter.
68
69
69
-
~~Sonar and Coveralls reporter will only provide valid reports, when source_path and/or test_path are provided, and ut_run is executed from your project's root path.~~
70
+
Sonar and Coveralls reporter will only provide valid reports, when source_path and/or test_path are provided, and ut_run is executed from your project's root path.
Invokes all Unit tests from schema/package "hr_test" with two reporters:
78
79
79
80
* ut_documentation_reporter - will output to screen and save output to file "run.log"
80
-
*~~ut_coverage_html_reporter - will report only on database objects that are mapping to file structure from "source" folder and save output to file "coverage.html"~~
81
+
* ut_coverage_html_reporter - will report only on database objects that are mapping to file structure from "source" folder and save output to file "coverage.html"
0 commit comments