Forum Discussion
omatzura
17 years agoSuper Contributor
Hi Chris,
thanks for your post! These are all good ideas.. soapUI Pro currently handles both the external and script libraries globally, ie they are not project-specific.. we would probably need to fix that first (ie to open up for project-specific jars and scripts, we could even store these in the project...)
The upcoming 1.7.6 release will improve on the "Import Settings" functionality to also (optionally) import scripts and external jars, which makes this a bit easier to move configurations around; you could distribute a zip containing only the bin\soapui-settings, bin\ext and bin\scripts folders which users could import from, once unzipped..)
Also, we are planning a revised "project-persistance" model, where each item is stored in a seperate file instead of everything in one file.. which would make teamwork and scm-integration alot more flexible..
A number of global properties are planned to be used in property-expansion, including something like a "projectDir" property which you could use to load your properties from.. ie you could specify something like "${#projectDir}/props.txt" in the PropertiesStep source file (or where ever else..)
Hope this is a bit comforting for now.. thanks for sharing your ideas, and don't hesitate to comment on/challenge the above!
regards,
/Ole
eviware.com
thanks for your post! These are all good ideas.. soapUI Pro currently handles both the external and script libraries globally, ie they are not project-specific.. we would probably need to fix that first (ie to open up for project-specific jars and scripts, we could even store these in the project...)
The upcoming 1.7.6 release will improve on the "Import Settings" functionality to also (optionally) import scripts and external jars, which makes this a bit easier to move configurations around; you could distribute a zip containing only the bin\soapui-settings, bin\ext and bin\scripts folders which users could import from, once unzipped..)
Also, we are planning a revised "project-persistance" model, where each item is stored in a seperate file instead of everything in one file.. which would make teamwork and scm-integration alot more flexible..
A number of global properties are planned to be used in property-expansion, including something like a "projectDir" property which you could use to load your properties from.. ie you could specify something like "${#projectDir}/props.txt" in the PropertiesStep source file (or where ever else..)
Hope this is a bit comforting for now.. thanks for sharing your ideas, and don't hesitate to comment on/challenge the above!
regards,
/Ole
eviware.com
Related Content
Recent Discussions
- 6 minutes agodipsthorat
- 4 hours agoisbiat
- 2 days agoarmygrad