Forum Discussion
I don't think you can raise a bug for SoapUI Open Source. But, if you face this issue in SoapUI NG, you can raise a ticket here - http://support.smartbear.com/product-list/
Thanks,
Samy
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others, Thanks. ↓↓↓
By the same bug, the -enableGUI parameter and whatever initGCTImer() does is broken as well. (see below).
For the real SoapUI developers: It will fixes plenty of bugs in the Commandline-Testrunner if you fix this issue. Thank you! :-)
The problem lies in the AnalyticsHelper:
private static boolean analyticsDisabled() {
Settings settings = SoapUI.getSettings();
which in turn creates a "DefaultSoapUICore" as there was none initialized before
which in turn sets isCommandLine to false.
As the AnalyticsHelper opens some GUI component if you did not enable/disable the analytics before, this is already a bug.
However - without analytics - in AbstractSoapUIRunner.run() the isCommandLine field is set twice.
public final boolean run() throws Exception {
if (SoapUI.getSoapUICore() == null) {
SoapUI.setSoapUICore(createSoapUICore(), true);
SoapUI.initGCTimer();
}
createSoapUICore() creates the DefaultSoapUICore which will set isCommandLine to false.
setSoapUICore is resetting to true just afterwards...
In my uninformed opinion the bug was inserted as the analytics were put inside. As I hate those analytics anyway, I will disable it in my source permamently... :-)
11:01:35,949 INFO [log] isCommandLine:true
11:01:35,951 INFO [log] isStandalone:false
Voilà! :-)
MFG
Heiko Studt