Forum Discussion
SmartBear_Suppo
Alumni
13 years agoHi,
Interesting discussion!
I would say, right now we don't have good support for sharing uniform settings across different machines.
Also, sharing soapui-settings.xml might be too cumbersome since it keeps references to projects location on user's file system and you might end up with more troubles. So for now, I can't suggest anything better than the way you are doing it.
After reading this thread, we have started to think about introducing global SoapUI level load script support. So, from SoapUI preference menu you can choose a script that will be run every time you start SoapUI, and this script will override soapui-settings.xml in case, you have conflicting values for the same property. And if you disable this preference it will just apply the settings saved on user's soapui-settings.xml as it is today. This means you still have to share your common load script and all SoapUI users within your organization need to select the script from preference. But this is better in the sense that, you will only have one script and users need to configure it only once. Upgrading and re-sharing can possibly be handled by some version control mechanism.
Feel free to comment on what do you think about the proposed feature or if you have any other suggestions. Once we are on the same page, I will create a new feature request.
Regards,
Shadid
SmartBear Sweden
Interesting discussion!
I would say, right now we don't have good support for sharing uniform settings across different machines.
Also, sharing soapui-settings.xml might be too cumbersome since it keeps references to projects location on user's file system and you might end up with more troubles. So for now, I can't suggest anything better than the way you are doing it.
After reading this thread, we have started to think about introducing global SoapUI level load script support. So, from SoapUI preference menu you can choose a script that will be run every time you start SoapUI, and this script will override soapui-settings.xml in case, you have conflicting values for the same property. And if you disable this preference it will just apply the settings saved on user's soapui-settings.xml as it is today. This means you still have to share your common load script and all SoapUI users within your organization need to select the script from preference. But this is better in the sense that, you will only have one script and users need to configure it only once. Upgrading and re-sharing can possibly be handled by some version control mechanism.
Feel free to comment on what do you think about the proposed feature or if you have any other suggestions. Once we are on the same page, I will create a new feature request.
Regards,
Shadid
SmartBear Sweden