Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibility to add debug-logging with several helpful information #89

pesse opened this Issue Jul 10, 2018 · 2 comments


None yet
2 participants
Copy link

commented Jul 10, 2018

To make support/debugging easier (see #88) we should have an option to enable debug-logging.
Information that should be included:

  • Java-Version
  • utPLSQL/cli/java-api version
  • ORACLE_HOME value

This comment has been minimized.

Copy link

commented Jul 10, 2018

For information, during my issue I tried utplsql info command but it doesn't work
Here the output (version 3.1.0):

V:\Tools\UnitTests\Jenkins\utPLSQL-cli\bin>utplsql info
Usage: utplsql [command] [command options]
    run      run tests
      Usage: run [options] <user>/<password>@//<host>[:<port>]/<service> OR
            <user>/<password>@<TNSName> OR
          -c, --color
            enables printing of test results in colors as defined by
            ANSICONSOLE standards
            Default: false
            override the exit code on failure, default = 1
            Default: 1
          -f, --format
            -f=reporter_name [-o=output_file [-s]] - enables specified format
            reporting to specified output file (-o) and to screen (-s)
            Default: []
          -p, --path
            run suites/tests by path, format: -p=[schema|schema:[suite
            ...][.test]|schema[.suite ...][.test]
            Default: []
          -scc, --skip-compatibility-check
            Skips the check for compatibility with database framework. CLI
            expects the framework to be most actual. Use this if you use CLI
            with a development version of utPLSQL-framework
            Default: false
            Comma-separated object list to exclude from the coverage report.
            Format: [schema.]package[,[schema.]package ...]. See coverage
            reporting options in framework documentation
            Comma-separated object list to include in the coverage report.
            Format: [schema.]package[,[schema.]package ...]. See coverage
            reporting options in framework documentation
            -source_path [-owner="owner" -regex_expression="pattern"
            -owner_subexpression=0 -type_subexpression=0
            -name_subexpression=0] - path to project source files
            Default: []
            -test_path [-regex_expression="pattern" -owner_subexpression=0
            -type_subexpression=0 -name_subexpression=0] - path to project
            test files
            Default: []

This comment has been minimized.

Copy link
Member Author

commented Jul 10, 2018

info command is part of the current develop-version and not yet released. We're working on making these things more clear :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.