Performance Testing Web Service Using SoapUI and SoapUI Pro

SOA
Service:
A repeatable business task Use defined protocols that describe how services pass and parse messages Accessible independently of implementation

SOA
An Architectural style that supports integrating business as linked services

SOAP & WSDL

SOAP
SOAP stands for Simple Object Access Protocol SOAP is a communication protocol SOAP is for communication between applications SOAP is a format for sending messages SOAP is platform/language independent

WSDL
WSDL is a document written in XML. The document describes a Web service. It specifies the location of the service and the operations (or methods) the service exposes.

SOAP UI
Web Service Testing Tool for Service Oriented Architecture Today
Set up a test project Add a WSDL that defines the Web Service Make some Requests Set up a Load Test Report the Results

What do we need ?
WSDL Sample Request URL Data

Single User Test

Number of concurrent Threads

Iteration Delay

Duration of the Test/Number of Cycles

CSV Format

CSV Format

Secured ServicesAdd Certificate

Configure Outgoing Configuration

Add and Assign Endpoint URLs

Add and Assign Endpoint URLs

 Following are the parameters which will help you define the load for your test : Threads : Number of virtual users or threads which will send out the WebService request to provided endpoint. Startegy : Simple is the default load test stratergy type to be used. In this all the multiple request would be sent in the sequence. Other stratergy like script, burst, grid, fixed rate can be used to define the different pattaern of load generation. Test Delay : This is the number of milliseconds delay to be introducted between 2 successive tests. It generally calculates the value based on Random number provided.

 Random : This number together will test delay will generate the random time, which will be introduced as delay. Limit : It defined the limit (in term of seconds, total run, runs per thread) for which you want to execute your load test. Also, you can select any specific test step from the load test list and by right clicking add some basic assertion to decide on the status of your load test. So based on load test strategy used you can assert if the number of maximum or step TPS (transaction per second) has reached a certain threshold. A simple scenario to perform a Load test for 20 users, 200 ms test delay and for 5 min, would have following values : Thread = 20 Strategy = Simple Test delay = 200 Random = 0.5 Limit = 300 Seconds