KBEC-00008 - Using Parasoft’s SOATest product with CloudBees CD (CloudBees Flow)

Article ID:360033195231
2 minute readKnowledge base
On this page


To run Parasoft SOATest tests in CloudBees CD (CloudBees Flow) steps, review this article.


The ParaSoft SOATest product can be invoked from the command line. Instructions from the Parasoft SOATest FAQ are included below:

If you would like to run SOAPtest from a command line, use a script file. Run your functional and load tests in command-line mode. To run from the command line with a script, use the following command:

On Windows:

st.exe -cmd -run SCRIPT


soaptest -cmd -run SCRIPT

Running functional tests

To run functional tests, the SCRIPT must contain the following:

runtest <"LocationOfProjectFile\ProjectFileName.tst"> [-reportHTML | ec:-reportXML] <"LocationToWriteReport\reportFile"> [-mail [ec:-attach] [from:address] to:address1[ec:,address2,...]]

For example, on Windows the SCRIPT file might contain the following:

runtest "C:\home\tests\project\tests\ProjectFile.tst" -reportHTML "C:\home\tests\project\reports%d_report.html" -reportXML "C:\home\tests\project\reports%d_report.xml"

(%d appends the current date to the file name)

Also, you can send generated reports via email by using the -mail option. The optional -attach flag sends the report as an attachment, otherwise the report is sent as the email body. The from: parameter is optional also, and sets the email’s sender field. The to: parameter is required and is a comma-separated list (without spaces) of email addresses to send the report to. For example:

runtest "C:\home\tests\project\tests\ProjectFile.tst" -reportHTML "C:\home\tests\project\reports%d_report.html" -mail -attach from:reporter@parasoft.com to:user1@parasoft.com,user2@parasoft.com
The -management option can be used in conjunction with the -reportHTML option to generate a "Management" view HTML report.

Running load tests

To run load tests, the SCRIPT contains the following:

open <"LocationOfProjectFile\ProjectFileName.tst">loadtest [ec:-minutes] <# of minutes> [ec:-report] <"LocationToSaveBinaryReport\loadtest.rpt"> [ec:-html] <"LocationToSaveHTMLReport"> <"ScenarioName">

For example, on Windows the SCRIPT file might contain the following:

open "C:\home\tests\project\tests\ProjectFile.tst"loadtest -minutes 1 -report "C:\home\tests\project\reports\loadtest.rpt" -html "C:\home\tests\tutorial\reports" "Steady Load"

Starting the load test server

To run the Load Test Server on Port 8999, specify the port number in the command-line argument such as:

st.exe -loadtestserver 8999

If you are starting the SOAtest Load Test Server from an icon shortcut, simply modify the shortcut properties.

Changing the endpoint router URL from a script file

To change the endpoint router URL dynamically within a script file, use the following command:

-router [ec:-matchWhole] <"searchURI"> <"replaceURI">

For example, to change your endpoint from https://soaptest.parasoft.com/endpoint-1 to https://soaptest.parasoft.com/endpoint-2, your script file might contain the following:

runtest "C:\home\tests\project\tests\ProjectFile.tst" -router -matchWhole https://soaptest.parasoft.com/endpoint-1 https://soaptest.parasoft.com/endpoint-2 -report -outputErrors "C:\home\tests\project\reports%d_report.html" -html -report -outputErrors "C:\home\tests\tutorial\reports%d_report.xml" -xml
To replace all router endpoints with a specific endpoint, rather than specifying a "searchURI" string, you can simply use the '*' wildcard in the following format:
-router [ec:-matchWhole] * <"replaceURI">

Running all project files within a directory

To run all project files within a directory, use the following command:

-all <"ProjectFileDirectory">

For example:

st.exe -cmd -runtest -all "C:\home\tests\project\tests"