Skip to main content

Command line execution of soapUI project

We run SoapUI project using SoapUI GUI interface.  SoapUI also provide set off batch files to execute soapUI tests from command line without using SoapUI GUI interface. 

Following are the runner scripts inside installed SoapUI bin folder.
1. testrunner.bat : this is use to run functional test using command line.
2. loadtestrunner.bat: This is used to run soapui load testing using command line.
3. mockservicerunner.bat:  This is used to run soapui mock services using command line.
4. toolrunner.bat: This is used to launch soapui tools.
5. securitytestrunner.bat: This command is used to run security tests

Note: setup soaui bin folder path into your system variable path.

Command Line soapui tests execution:

1. Open command prompt and got to your created soapui project.
2. Run command > testrunner {SoapProjectName}.xml

3. After running test you should see some text file is generated in root.
4. We can run test suite or test case using testrunner command. as below:

testrunner –c "APITestCase" -r SampleTest-soapui-project.xml

Where “APITestCase is test name and “SampleTest-soapui-project.xml” is soapui project. Here I use –r flag so that after execution console summary look like below.

SoapUI 4.5.1 TestCaseRunner Summary
-----------------------------
Time Taken: 24493ms
Total TestSuites: 0
Total TestCases: 1 (0 failed)
Total TestSteps: 2
Total Request Assertions: 0
Total Failed Assertions: 0
Total Exported Results: 0

5. Following are the testrunner flags and its description.

usage: testrunner [options]
 -v    Sets password for soapui-settings.xml file
 -t    Sets the soapui-settings.xml file to use
 -A    Turns on exporting of all results using folders instead of lon
       filenames
 -D    Sets system property with name=value
 -G    Sets global property with name=value
 -I    Do not stop if error occurs, ignore them
 -M    Creates a Test Run Log Report in XML format
 -P    Sets or overrides project property with name=value
 -S    Saves the project after running the tests
 -a    Turns on exporting of all results
 -c    Sets the testcase
 -d    Sets the domain
 -e    Sets the endpoint
 -f    Sets the output folder to export results to
 -h    Sets the host
 -i    Enables Swing UI for scripts
 -j    Sets the output to include JUnit XML reports
 -m    Sets the maximum number of TestStep errors to save for each  testcase
 -p    Sets the password
 -r    Prints a small summary report
 -s    Sets the testsuite
 -u    Sets the username
 -w    Sets the WSS password type, either 'Text' or 'Digest'
 -x    Sets project password for decryption if project is encrypted

Labels:

Comments

Post a Comment

Popular posts from this blog

JMeter Exceeded Maximum Number of Redirects Error Solution

While running performance test, JMeter allows maximum 5 redirects by default. However, if your system demands more than 5 redirects, it may result in JMeter exceeded maximum number of redirects error. In this post, we have listed down steps to overcome this error. Actual error in JMeter: Response code: “Non HTTP response code: java.io.IOException” Response message: “Non HTTP response message: Exceeded maximum number of redirects: 5” This error is noticed because  JMeter  allows maximum 5 redirects by default and your system may be using more than 5 redirects. You need to increase this count to more than 5 in jmeter.properties file. Follow below steps to achieve this. Navigate to /bin directory of your JMeter installation. Locate jmeter.properties file and open it in any editor. Search for “httpsampler.max_redirects” property in opened file. Uncomment the above property by removing # before it. Change to value to more than 5 Eg. 20. Save the file and restart JMet...
Post a Comment
Read more

Performance Testing in the Cloud with JMeter & AWS

JMeter is a wonderful tool  to stress test your website and  your application architecture , however if you are trying to simulate many users (>1000) one JMeter instance (=pc) will not be sufficient. You will have to set up a JMeter cluster with multiple machines. JMeter is capable or running  distributed tests , but it comes with limitations. Since most of us don’t have multiple servers laying around somewhere, we usually go to cloud service providers like  AWS , spin up a couple of  EC2 instances  and turn them off whenever we’re done. Here is the problem, JMeter uses  Java RMI (Remote Method Invocation)  to communicate to its slaves, but these connections require all machines to be on the same subnet and this is not feasible with EC2 instances. Below, I explain how to get around this problem using a 3 node configuration in AWS to execute tests. I assume that you have a written the test already and have the .jmx file r...
Post a Comment
Read more

Difference Between Redirect Automatically and Follow Redirects in JMeter

In this post, we will highlight important difference between Redirect Automatically and Follow Redirects options. These options are found in HTTP Request sampler of JMeter. Knowing the difference will help you decide your performance test strategy. When you check Redirect Automatically option, JMeter will not consider redirect as separate HTTP request. This in turn may result as lower response time in your overall performance test. Whereas Follow Redirect option will consider each redirection as separate requests. This may result in comparatively higher response time. This only has any effect if “Redirect Automatically” is not enabled. To see the difference between these two, record a sample script and run it by checking Redirect Automatically and Follow Redirects option. The second option will generate more requests in your result listener. As you can see from the above post, knowing the difference between Redirect Automatically and Follow Redirects option makes difference i...
Post a Comment
Read more