Forum Discussion
erichmusick
13 years agoNew Contributor
I added a Setup script to my project as a workaround; this seems to solve the problem. However, it certainly seems to be a defect in SoapUI.
Here is my command line:
call "C:\Program Files\SmartBear\soapUI-Pro-4.5.1.1-SNAPSHOT\bin\testrunner.bat" -I -a -A -j -ESystemTestB -r -f"C:\Jenkins\jobs\Tests_SYS\workspace\reports" -POutputDirectory=C:\Jenkins\jobs\SYS\workspace\reports -PEnvironmentVar=SystemTestB -tC:\Jenkins\customSettings\soapui-settings.xml "C:\Jenkins\customSettings\Integration15Tests"
It should be sufficient to use only the first, but adding the second, in conjunction with the groovy script above seemed to solve my problem.
def env = project.getPropertyValue("EnvironmentVar")
log.info "Environment param = " + project.getPropertyValue("EnvironmentVar")
log.info "Pointing to environment = " + project.getActiveEnvironmentName()
if (env != null && env != "") {
project.setActiveEnvironment(env)
log.info "Now Pointing to environment = " + project.getActiveEnvironmentName()
}
Here is my command line:
call "C:\Program Files\SmartBear\soapUI-Pro-4.5.1.1-SNAPSHOT\bin\testrunner.bat" -I -a -A -j -ESystemTestB -r -f"C:\Jenkins\jobs\Tests_SYS\workspace\reports" -POutputDirectory=C:\Jenkins\jobs\SYS\workspace\reports -PEnvironmentVar=SystemTestB -tC:\Jenkins\customSettings\soapui-settings.xml "C:\Jenkins\customSettings\Integration15Tests"
It should be sufficient to use only the first, but adding the second, in conjunction with the groovy script above seemed to solve my problem.