Skip to main content

Performance testing using soapUI

I would like to show you performance testing of webservices using soap ui.
Performance testing of web services is not just running SOAP or XML messages in a loop to run the service. It should be a well-planned activity which must be aligned with the performance expectations of the overall service-oriented solution.  You can run multiple type of performance test such as SOAP , JSON, XML format messaging through a single interface
SoapUI allows users to configure various load testing options such as delays in between threads to simulate real-world use cases and run tests in burst mode to stress test services.

How to create Load Test: Just go to Navigation bar of soapUI click on your create soaui project and expand test case. Right click on “load test” options, enter load test name on opened window and click on OK button. Your created load test window looks like as below.


As in above screenshot have two soap ui test method “login” and “Register” both methods are automatically reflect on load test window.

Load Test Limit: load test limit define interval of test case execution. SoapUI has two variable for limit 1. Limit value 2. Limit type. Limit type has three options “Total Runs”, “seconds” “Runs per thread”
1. Total Runs limit type is used to set the number of times the TestCase needs to be executed during each load test run.
2. Seconds, lumit type is used to be execute of load test for a particular time.
3 .Runs per thread limit type is used to set number of time to be execute per thread of TestCase.


Threads: Threads act as virtual users in a load test. If the thread count is set as N, soapUI creates N number of clones of the associated TestCase and executes them.

Load test strategies: following type load strategies are used in soau UI
1. Simple
2. Burst
3. Thread
4. Variance



Set any load strategy as your requirement and click on run icon. After execution your window looks like as below screen.
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