Forum Discussion
Hi apattanayak,
I'm sorry, but I don't fully understand this statement:
"As soon as, there is an independent groovy script, which is outside the project xml, can not find those dependencies."
Can you please provide more details about your configuration and errors that you get?
Hi Nastya_Khovrina , sorry for late response.
in my local drive directory structure looks like
test-automation/xxx/ProjectA
Inside projectA, corresponding project.xml is present with multiple test cases. Each test case has some groovy scripts. In local machine, we manually copy the required dependency under this location C:\Program Files (x86)\SmartBear\SoapUI-5.4.0\lib and it works fine.
I added a seperate groovy script under test-automation/groovy-lib/ . I call this script from the test cases present under test-automation/xxx/ProjectA.
In jenkins, whenGroovy script which is present under project.xml, it finds all the dependency(common groovy lib and also in house jars). And In jenkins, for all of our internal Jars, we use 'Additional classpath' under 'build environment' step. They work all fine.
From the test case, the groovy script CreateUser.groovy is getting called, this is present under test-automation/groovy-lib/ does not find the related dependency. But when that script is present under test-automation/xxx/ProjectA/ProjectA.xml it finds all the dependencies.
Any suggestion would be highly appreciated. Thank you.
Thanks,
Arindam
Related Content
Recent Discussions
- 7 days agoemoya