Forum Discussion
redfish4ktc2
11 years agoSuper Contributor
Anonymous Support
I have the folowing 3 questions
You previously answered to Siking question
This is the current behaviour but do you plan in the future to also add the license check to the SoapUI-Pro Maven plugin as well?
About the "courtesy mode" currently implemented, I have noticed a behaviour difference between the GUI and the test runner from the command line:
And I guess starting the cli test runner from the GUI also prevent tests to be runned!
So my question is: do you plan to remove such a limitation in the future?
About the license for CI server
AFAIK, the license installation/activation is performed using a GUI. How can this be managed in environment such Linux without X11 where no GUI can be started?
This means that for now, you prevent pro users to run tests in that kind of environment. See viewtopic.php?f=13&t=25075
Do you have any workaround to mitigate the issue?
To conclude, you may have noticed that I am not a fan of such technical limitations especially in CI environments. I agree that you can make that kind of choice to save your business or for any other reasons. But in that case, I would like to have a clear warning/explanation along with the release notes/changelog to avoid misunderstandings.
Thanks in advance for your answers
Thomas
I have the folowing 3 questions
You previously answered to Siking question
Does this apply to the SoapUI-Pro Maven plugin as well?
No, this does not apply to the SoapUI Pro maven plugin
This is the current behaviour but do you plan in the future to also add the license check to the SoapUI-Pro Maven plugin as well?
About the "courtesy mode" currently implemented, I have noticed a behaviour difference between the GUI and the test runner from the command line:
- GUI: Pro-specific TestSteps (DataSource, DataSink, etc.) are still executed as part of a TestCase execution but can’t be created or modified in your tests(source: http://www.soapui.org/Getting-Started/i ... rtesy-mode)
- CLI: no test cannot be runned
And I guess starting the cli test runner from the GUI also prevent tests to be runned!
So my question is: do you plan to remove such a limitation in the future?
About the license for CI server
AFAIK, the license installation/activation is performed using a GUI. How can this be managed in environment such Linux without X11 where no GUI can be started?
This means that for now, you prevent pro users to run tests in that kind of environment. See viewtopic.php?f=13&t=25075
Do you have any workaround to mitigate the issue?
To conclude, you may have noticed that I am not a fan of such technical limitations especially in CI environments. I agree that you can make that kind of choice to save your business or for any other reasons. But in that case, I would like to have a clear warning/explanation along with the release notes/changelog to avoid misunderstandings.
Thanks in advance for your answers
Thomas
Related Content
- 9 years ago
- 5 years ago
- 6 years ago
- 6 years ago
Recent Discussions
- 22 days ago