UPDATE: Issue appears to be due to a bug in JDK12.
I am new to ReadyAPI. But, here is a suggestion. Try to find out where your ReadyAPI logs are in MacOS and look for clues in ready-api.log and/or ready-api-errors.log files. Post any log errors here as they could help in diagnosing your issue.
Btw, for Windows, logs are stored here:
c:\users\username\.readyapi\logs
Look for a similar location in MacOS.
The logs that get created give no additional details. This is the ready-api.log file (sanitized for personal information)
2020-10-28 15:00:27,541 INFO [license] ReadyAPI 3.4.0 (build 6037) started - System properties: {OS=Mac OS X, User name=XXXXX}
2020-10-28 15:00:27,758 INFO [DefaultSoapUICore] ReadyAPI settings were initialized from [XXXXX/.readyapi/readyapi-settings.xml]
2020-10-28 15:00:27,786 INFO [SoapUIExtensionClassLoader] "/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/ext/sqljdbc42.jar" has been added to the classpath.
2020-10-28 15:00:27,786 INFO [SoapUIExtensionClassLoader] "/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/ext/postgresql-9.3-1102.jdbc41.jar" has been added to the classpath.
2020-10-28 15:00:27,786 WARN [SoapUIExtensionClassLoader] The path to the custom library is not specified.
2020-10-28 15:00:27,828 INFO [DefaultSoapUICore] 2 JDBC drivers have been registered from the directory bin/ext: [com.microsoft.sqlserver.jdbc.SQLServerDriver, org.postgresql.Driver].
2020-10-28 15:00:28,006 INFO [DefaultSoapUICore] Adding listeners from [/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/listeners/demo-listeners.xml]
2020-10-28 15:00:28,022 WARN [SoapUIJasperReportManager] The report directory "XXXXX/report_templates/reports" does not exist. The default report directory will be used.
There is no data written to ready-api-errors.log or global-groovy.log
NickMitricka I found your support case (00456514), looks like our engineers are waiting for some info from you. Please keep working with them there. The ReadyAPI Community will also appreciate it if you post the final solution here. Thank you!
UPDATE: Issue appears to be due to a bug in JDK12.
