soapUI settings through script
In order to have uniform settings on developer machines we enforce many best practices through groovy script through project load script. This is to ensure that even though developer manually changed ...
Forum Discussion
Nice proposal Shadid !
In my opinion there could be couple of solutions.
1. First one would be more simpler and coding-less solution. I think I had given that proposal in some other thread.
Please refer to this one:
http://www.soapui.org/forum/viewtopic.php?f=2&t=15841
This solution would be as simple as exporting master preferences from one machine and then importing same preferences on any developer machine. The file which will be exported should be able to be maintained in the version control tool. SoapUI-settings.xml file is also same but it stores many developer machine specific details. The one which I am proposing should be developer machine neutral, may be a child file of the soapUI-settings file. This type of solution is available almost in all programming IDE in the form of coding best practises.
This has advantage that it is really simple solution for soapUI users (for you guys more toil may be). They need not to be worry about searching API and implementing any solution through code. The disadvantage is that it requires governance that every developer must have imported master preferences file on their machine however that is organisations to enforce this.
2. Second solution could be exactly what you are proposing. This one requires API knowledge. May be you guys can provide some sample snippets. This solution doesn't require any additional governance. One more advantage I see is for some other purposes many times developer could require global scripting, your new place can be extended for that purpose as well.
Thank you.
In my opinion there could be couple of solutions.
1. First one would be more simpler and coding-less solution. I think I had given that proposal in some other thread.
Please refer to this one:
http://www.soapui.org/forum/viewtopic.php?f=2&t=15841
This solution would be as simple as exporting master preferences from one machine and then importing same preferences on any developer machine. The file which will be exported should be able to be maintained in the version control tool. SoapUI-settings.xml file is also same but it stores many developer machine specific details. The one which I am proposing should be developer machine neutral, may be a child file of the soapUI-settings file. This type of solution is available almost in all programming IDE in the form of coding best practises.
This has advantage that it is really simple solution for soapUI users (for you guys more toil may be). They need not to be worry about searching API and implementing any solution through code. The disadvantage is that it requires governance that every developer must have imported master preferences file on their machine however that is organisations to enforce this.
2. Second solution could be exactly what you are proposing. This one requires API knowledge. May be you guys can provide some sample snippets. This solution doesn't require any additional governance. One more advantage I see is for some other purposes many times developer could require global scripting, your new place can be extended for that purpose as well.
Thank you.