We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Forum Discussion
Solved
How do we integrate soapUI test created using soap UI Free version
Hello team, How do we integrate and run soap UI tests as part of continuous Integration process ? our Soap UI tests are created using SOAP UI free version .Can anyone outline steps ?
when start gets removed .....i don't see the build running on the build exectutor status window however build still got executed and failed with this below message. I tried command line option and testrunner.bat is gettting called from commandline with no issues
Console Output
Started by user admin
Building in workspace C:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests
[SoapUIAutomatedTests] $ cmd /c call C:\Windows\TEMP\jenkins3244711319342882945.batC:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests>"C:\Program Files (x86)\SmartBear\SoapUI-5.2.1\bin\testrunner.bat" -sGetRenlBatchesTestSuite -cGetRenbatches -r -a -f"C:\Program Files\SmartBear\SoapUI-5.2.1\bin\TestResults" -I C:\Users\XYZuser\GitHub\ren-api2\Tests\Automated_Test\GetRenBatches-soapui-project.xml
The system cannot find the path specified.C:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests>exit 3
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILUREI have had testrunner running on jenkins build
The only difference I am using a pro version
open source should be not much different
Is that the correct location
"C:\Program Files (x86)\SmartBear\SoapUI-5.2.1\bin\testrunner.bat"
Try your command using command line prompt
I usually do that before adding it to my jenkins build.
when start gets removed .....i don't see the build running on the build exectutor status window however build still got executed and failed with this below message. I tried command line option and testrunner.bat is gettting called from commandline with no issues
Console Output
Started by user admin
Building in workspace C:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests
[SoapUIAutomatedTests] $ cmd /c call C:\Windows\TEMP\jenkins3244711319342882945.bat
C:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests>"C:\Program Files (x86)\SmartBear\SoapUI-5.2.1\bin\testrunner.bat" -sGetRenlBatchesTestSuite -cGetRenbatches -r -a -f"C:\Program Files\SmartBear\SoapUI-5.2.1\bin\TestResults" -I C:\Users\XYZuser\GitHub\ren-api2\Tests\Automated_Test\GetRenBatches-soapui-project.xml
The system cannot find the path specified.
C:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests>exit 3
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE
I have had testrunner running on jenkins build
The only difference I am using a pro version
open source should be not much different
Is that the correct location
"C:\Program Files (x86)\SmartBear\SoapUI-5.2.1\bin\testrunner.bat"
Try your command using command line prompt
I usually do that before adding it to my jenkins build.
Like i mentioned earlier in my post I was able to run using command line prompt and also based on the log it is reading from correct location as highlightened in bold -"C:\Program Files (x86)\SmartBear\SoapUI-5.2.1\bin\testrunner.bat"
Console Output
Started by user admin
Building in workspace C:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests
[SoapUIAutomatedTests] $ cmd /c call C:\Windows\TEMP\jenkins3244711319342882945.batC:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests>"C:\Program Files (x86)\SmartBear\SoapUI-5.2.1\bin\testrunner.bat" -sGetRenlBatchesTestSuite -cGetRenbatches -r -a -f"C:\Program Files\SmartBear\SoapUI-5.2.1\bin\TestResults" -I C:\Users\XYZuser\GitHub\ren-api2\Tests\Automated_Test\GetRenBatches-soapui-project.xml
The system cannot find the path specified.C:\Program Files (x86)\Jenkins\workspace\SoapUIAutomatedTests>exit 3
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURETurned out to be issue on my end . I was using incorrect arguments. Path location seemed to be incorrect as mentioned (I overlooked) . I was able to correct the path and it worked like a charm
I appreciate all your suggestions and they were indeed helpful in trouble shooting issue