Skip to content

NullPointerException when specifying -o key without -f key #170

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.

Sign up for GitHub

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

Jump to bottom
Closed
alesana-san opened this issue Nov 28, 2019 · 0 comments · Fixed by #171
Closed

NullPointerException when specifying -o key without -f key #170

alesana-san opened this issue Nov 28, 2019 · 0 comments · Fixed by #171
Assignees
@pesse
Labels
bug
Milestone
3.1.9

Comments

@alesana-san
Copy link

Hey!

My preset is:

C:\Users\Shiryaev1-RY>utplsql.bat info "some_user"/"q1w2e3r4t5y6u7i8o9p0"@local_pdb
utPLSQL-cli 3.1.8-SNAPSHOT.local
utPLSQL-java-api 3.1.8.546
utPLSQL 3.1.6.2735

Here's what I get when I put -o without -f specified:

D:\repos\sp-db-beholder>D:\soft\utPLSQL-cli\bin\utplsql.bat run some_user/q1w2e3r4t5y6u7i8o9p0@local_pdb -p=SP.UT_SP_HAND_MR.XFER_SYNC_WAIT_ERR_CALL -d -o=output.txt
2019-11-28 13:51:19 [main] INFO  org.utplsql.cli.RunAction - ############# utPLSQL cli ##############
#                                      #
#   utPLSQL-cli 3.1.8-SNAPSHOT.local   #
#   utPLSQL-java-api 3.1.8.546         #
#   Java-Version: 1.8.0_221            #
#   ORACLE_HOME: null                  #
#   NLS_LANG: null                     #
#                                      #
#   Thanks for testing!                #
#                                      #
########################################
2019-11-28 13:51:19 [main] INFO  org.utplsql.cli.RunAction -
2019-11-28 13:51:20 [main] INFO  o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:thin:****/****@local_pdb
2019-11-28 13:51:20 [main] INFO  org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.6.2735
2019-11-28 13:51:20 [main] INFO  org.utplsql.cli.RunAction - Oracle-Version: 12.2.0.1.0
java.lang.NullPointerException
        at org.utplsql.cli.ReporterOptions.getReporterName(ReporterOptions.java:37)
        at org.utplsql.cli.ReporterManager.initReporters(ReporterManager.java:89)
        at org.utplsql.cli.RunAction.initReporters(RunAction.java:219)
        at org.utplsql.cli.RunAction.doRun(RunAction.java:70)
        at org.utplsql.cli.RunAction.run(RunAction.java:121)
        at org.utplsql.cli.RunPicocliCommand.run(RunPicocliCommand.java:254)
        at org.utplsql.cli.Cli.runPicocliWithExitCode(Cli.java:44)
        at org.utplsql.cli.Cli.main(Cli.java:13)

And when I specify -f flag everything works as expected: file is created, termination is normal:


D:\repos\sp-db-beholder>D:\soft\utPLSQL-cli\bin\utplsql.bat run some_user/q1w2e3r4t5y6u7i8o9p0@local_pdb -p=SP.UT_SP_HAND_MR.XFER_SYNC_WAIT_ERR_CALL -d -f=UT_DOCUMENTATION_REPORTER -o=output.txt
2019-11-28 13:51:41 [main] INFO  org.utplsql.cli.RunAction - ############# utPLSQL cli ##############
#                                      #
#   utPLSQL-cli 3.1.8-SNAPSHOT.local   #
#   utPLSQL-java-api 3.1.8.546         #
#   Java-Version: 1.8.0_221            #
#   ORACLE_HOME: null                  #
#   NLS_LANG: null                     #
#                                      #
#   Thanks for testing!                #
#                                      #
########################################
2019-11-28 13:51:41 [main] INFO  org.utplsql.cli.RunAction -
2019-11-28 13:51:42 [main] INFO  o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:thin:****/****@local_pdb
2019-11-28 13:51:42 [main] INFO  org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.6.2735
2019-11-28 13:51:42 [main] INFO  org.utplsql.cli.RunAction - Oracle-Version: 12.2.0.1.0
2019-11-28 13:51:43 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_DOCUMENTATION_REPORTER, ID: 9866E6142AFD94BDE053020012ACFF1C
2019-11-28 13:51:43 [pool-1-thread-1] INFO  org.utplsql.cli.RunTestRunnerTask - Running tests now.
2019-11-28 13:51:43 [pool-1-thread-1] INFO  org.utplsql.cli.RunTestRunnerTask - --------------------------------------
2019-11-28 13:51:43 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - TestRunner initialized
2019-11-28 13:51:43 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - Running on utPLSQL v3.1.6.2735
2019-11-28 13:51:43 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - Initializing reporters
2019-11-28 13:51:43 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - Running tests
2019-11-28 13:51:43 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - Running tests finished.
2019-11-28 13:51:44 [main] INFO  org.utplsql.cli.RunAction - --------------------------------------
2019-11-28 13:51:44 [main] INFO  org.utplsql.cli.RunAction - All tests done.
````

I guess if by default I get `UT_DOCUMENTATION_REPORTER` output on the screen without specifying `-f` key so I should be getting the same reporter when it's written to file.
@pesse pesse self-assigned this Dec 10, 2019
@pesse pesse added this to the 3.1.9 milestone Dec 10, 2019
@pesse pesse added the bug label Dec 10, 2019
pesse added a commit that referenced this issue Dec 10, 2019
@pesse
Make ut_documentation_reporter the default for commandline
ebda736 
Fixes #170
@pesse pesse mentioned this issue Dec 10, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pesse pesse

Labels
bug
Projects
None yet
Milestone
3.1.9
Development

Successfully merging a pull request may close this issue.

Bugfix/Locale-Info and Nullpointer utPLSQL/utPLSQL-cli
2 participants
@pesse @alesana-san