SOAP UI

SOAP UI Author Ashish Ranjeet SinghSoap UIis an open-source web service testing application for service-oriented architectures (SOA) and representational state transfers (REST). HTTP protocol is used. Its functionality covers web service inspection, invoking, development, simulation and mocking, functional testing, load and compliance testing. It is primarily use to test middle office applications in any architectures. It is built entirely on Java platform. It uses Swings for UI. It supports Eclipse, Netbeans Java development tools .It is generally used to hit web services . It was developed by eviware and now it has ben taken over by Smart Bear.

Basic IntroductionSo the first question would be what was the need of SAOP UI ?In a general there are three main components in any system i.e. Front OfficeMiddle Office Backend ( generally Database)Front office is like what we have websites like Metropcs.com , My TMO. So in order to test them we just do sanity checks on site by logging in and checking all the flows. So we have this way of testing the front office.Need of SOAP UINow in web based systems the interaction between the front office and backend is by using web services.Now there is a need to test these web services as well.So this where SOAP UI comes into the picture. So, SOAP UI gives us a way to test the web services. And we use the URLs to invoke these services. Now for each operation of a web service there will be a request which will be automatically created once you import the project.Need of SOAP UINow the next question is , these requests are unfilled . So you need to pass the parameters in them. Now how to know what to fill in parameters in the request ?

So the answers is : Whenever a web service is developed , there will always be a document created , which will contain all the details about all the fields which will be present in the request and what all are the permissible parameters which can be passed. Some of the parameters would be optional and some will be mandatory to pass.

It basically has all info about the web service. It is generally called as STUS and is primarily possessed by developing team. Also note that the end points URLs which we use to fire the request will be different for different environments.

Use of SOAP UI in T MobileIn our project we are using the SOAP UI to test the web services which serves MY TMO and with the help of SOAP UI we are troubleshooting various issues.

Now here we are hitting web services in two ways.Hitting DirectlyThrough boomi layer (sort of tunneling)There are some requests like getprofile for which we hit the request on https://esoa-proxyweb.internal.t-mobile.com/genericesp/soap URL on PROD environment. This is a ESOA request. So here we are hitting the web service directly.However we also hit some of the web services through boomi layer. Here also in reality we are actually hitting the web service on ESOA only but then by tunneling through boomi layer. For boomi request there is no need to add

Use of SOAP UI in T MobileSOAPAction in header. However when we are directly hitting the ESOA we need to give the SOAP ACTION.In case of boomi request SOAPACTION is defined at boomi layer.

You can identify boomi request if xmlns:wss="http://www.boomi.com/connector/wss is present in the SOAP UI request.As of now we are hitting all the boomi requests on http://172.28.49.121/ws/soap URL.Use of SOAP UI in T MobileThanks Use of SOAP UI in T Mobile