[SOLVED]soapui 3.0.1 testrunner seems to be ignoring -t arguement
Hello,
I am using hudson to run automated builds and using soapui 2.5.2 I had the following soapui batch process which worked fine.
cmd.exe /C testrunner.bat "%TFS_WORKFOLDER%\Integration_Environment\SmartRecommendationsService\SmartRecommendations-soapui-project.xml" -t"%TFS_WORKFOLDER%\ Integration_Environment\Integration-soapui-settings.xml" -f"F:\HudsonResults\%JOB_NAME%\%BUILD_NUMBER%\SmartRecommendationsService" -j -g
the Integration-soapui-settings.xml in our framework specify the groovy library.
When I upgraded to 3.0.1 I noticed a lot of test failures. Looking at the hudson logs seems to indicate that soapui is not picking up the script library location and is using the default setting.xml file.
hudson Log:
F:\Programs\soapUI-Pro\bin>cmd.exe /C testrunner.bat "F:\hudson_workspace\jobs\Phase-Neon-Integration\workspace\.\Integration_Environment\SmartRecommendationsService\SmartRecommendations-soapui-project.xml" -t"F:\hudson_workspace\jobs\Phase-Neon-Integration\workspace\.\ Integration_Environment\Integration-soapui-settings.xml" -f"F:\HudsonResults\Phase-Neon-Integration\23\SmartRecommendationsService" -j -g
JAVA_HOME is not set, unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
soapUI Pro 3.0.1 TestCase Runner
log4j:WARN No appenders could be found for logger (com.eviware.soapui.impl.coverage.report.CoverageBuilder).
log4j:WARN Please initialize the log4j system properly.
Configuring log4j from [F:\Programs\soapUI-Pro\bin\soapui-log4j.xml]
18:52:27,567 INFO [SoapUI] Added [file:/F:/Programs/soapUI-Pro/bin/ext/sqljdbc.jar] to classpath
18:52:27,957 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Documents and Settings\cpsautomation\soapui-settings.xml]
18:52:28,629 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [F:\hudson_workspace\jobs\Production_Monitor\workspace\Groovy]
This is a high priority issue.
Ali
I am using hudson to run automated builds and using soapui 2.5.2 I had the following soapui batch process which worked fine.
cmd.exe /C testrunner.bat "%TFS_WORKFOLDER%\Integration_Environment\SmartRecommendationsService\SmartRecommendations-soapui-project.xml" -t"%TFS_WORKFOLDER%\ Integration_Environment\Integration-soapui-settings.xml" -f"F:\HudsonResults\%JOB_NAME%\%BUILD_NUMBER%\SmartRecommendationsService" -j -g
the Integration-soapui-settings.xml in our framework specify the groovy library.
When I upgraded to 3.0.1 I noticed a lot of test failures. Looking at the hudson logs seems to indicate that soapui is not picking up the script library location and is using the default setting.xml file.
hudson Log:
F:\Programs\soapUI-Pro\bin>cmd.exe /C testrunner.bat "F:\hudson_workspace\jobs\Phase-Neon-Integration\workspace\.\Integration_Environment\SmartRecommendationsService\SmartRecommendations-soapui-project.xml" -t"F:\hudson_workspace\jobs\Phase-Neon-Integration\workspace\.\ Integration_Environment\Integration-soapui-settings.xml" -f"F:\HudsonResults\Phase-Neon-Integration\23\SmartRecommendationsService" -j -g
JAVA_HOME is not set, unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
soapUI Pro 3.0.1 TestCase Runner
log4j:WARN No appenders could be found for logger (com.eviware.soapui.impl.coverage.report.CoverageBuilder).
log4j:WARN Please initialize the log4j system properly.
Configuring log4j from [F:\Programs\soapUI-Pro\bin\soapui-log4j.xml]
18:52:27,567 INFO [SoapUI] Added [file:/F:/Programs/soapUI-Pro/bin/ext/sqljdbc.jar] to classpath
18:52:27,957 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Documents and Settings\cpsautomation\soapui-settings.xml]
18:52:28,629 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [F:\hudson_workspace\jobs\Production_Monitor\workspace\Groovy]
This is a high priority issue.
Ali
