[Resolved] Script Library
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2014
09:59 AM
07-02-2014
09:59 AM
[Resolved] Script Library
Hi
Recently we created one class in groovy script library. We are successfully able to access the class from the soapUI's groovy step.
When I deployed the code into the server where we do automation testing, it is not working. From the log I can make out that, soapUI is looking for the Script file in a folder which is an empty. Please refer below screen shot to understand in detail.
soapUI is looking for Script in the folder "rtc_5451". We create this temporary staging folder for each test run. The folder contains latest source from the source control. We do delete the folder once test execution is completed. Ideally soapUI should look for script library in "rtc_4771" which is directory created for the current test cycle. I do set script library path in the load script. You can notice that statement highlighted in yellow color towards the bottom side.
I think [SoapUIProGroovyScriptEngineFactory] is using older path which has been updated in the soapui-seetings.xml file in the previous run.
Why is this happening? Please guide us how can we update library path in the soapui-settings.xml just at the beginning of the test so that it is picked up correctly?
Recently we created one class in groovy script library. We are successfully able to access the class from the soapUI's groovy step.
When I deployed the code into the server where we do automation testing, it is not working. From the log I can make out that, soapUI is looking for the Script file in a folder which is an empty. Please refer below screen shot to understand in detail.
soapUI is looking for Script in the folder "rtc_5451". We create this temporary staging folder for each test run. The folder contains latest source from the source control. We do delete the folder once test execution is completed. Ideally soapUI should look for script library in "rtc_4771" which is directory created for the current test cycle. I do set script library path in the load script. You can notice that statement highlighted in yellow color towards the bottom side.
I think [SoapUIProGroovyScriptEngineFactory] is using older path which has been updated in the soapui-seetings.xml file in the previous run.
Why is this happening? Please guide us how can we update library path in the soapui-settings.xml just at the beginning of the test so that it is picked up correctly?
Regards,
LIT
This post in no way reflect any Policies of Liberty Information Technology Ltd.
LIT
This post in no way reflect any Policies of Liberty Information Technology Ltd.
11 REPLIES 11
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2014
02:01 AM
07-31-2014
02:01 AM
This has solved for me by not using global script library path rather using project level library path.
Regards,
LIT
This post in no way reflect any Policies of Liberty Information Technology Ltd.
LIT
This post in no way reflect any Policies of Liberty Information Technology Ltd.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2016
06:01 AM
11-25-2016
06:01 AM
This seems to be still an issue with SoapUI Pro 5.1.2. When running with SoapUIPro plugin in Jenkins the script library path is not set correctly.

- « Previous
-
- 1
- 2
- Next »
- « Previous
-
- 1
- 2
- Next »