top of page
  • Writer's picturekhyati sehgal

SoapUI Tutorial Part 1 : A world-class tour to SoapUI PRO.

Soap UI PRO is a tool wherein you just need to click on the actions available to you and you can make your imagination comes true. Services testing was never so easy before the make-believe fantasy of SoapUI PRO creators. I want to thank them before giving you a brief of the tool cum weapon as they say.

Why SoapUI?

SoapUi is a very powerfully built tool which is used for Services testing.

It is a tool that lets you take a world of clicks and when put to use, you can ease your life. More often than not, services testing is pondered as a tedious task as there are a lot of parameters, headers, requests, traffic, responses you need to take care of which can create chaos if not taken seriously. Of-times, we spot developers providing a service that we as a tester needs to inquire into against various payloads, multiple threads, etc.

This looks doable when we are taking into consideration one service. But what if we have only developed services and testing needs to be done on services and there is no UI developed as of now for the product. On that occasion, significant tools like SoapUI comes into the picture with the vital requirement. And not only tester, but developers can also get benefited from this tool. Let’s see how can we use SoapUI:

  1. First of all, there is some norms that you need to follow if you want to get familiar with SoapUI.

To add any request you need to follow a hierarchy : Project → Test Suite → Test Case → Test Step. And this test step will have the requests you want to fire and get a response from.

  1. Next, you have some SetUp and TearDown scripts placed at different levels of hierarchy and you can directly get advantage from them.

Project setup and teardown properties:

Test suite setup and teardown properties:

Test case setup and teardown properties:

  1. Features like events creation, database connections, etc can be done only on the project level. Once you are down in the hierarchy, say test case, then you can refer the parameters defined at the project level or test suite level, but not from the test step level. It follows a top-down approach, in short.

  1. For adding new database connection, via JDBC connection or as a JDBC test step, you need to import drivers and you can do it by adding the respective driver/jar in the Soapui/ext folder where Soapui is installed in your local machine.

  2. For any change, you want to incorporate in your tests you need to restart SoapUI. For example, you want to add some jars of say database like DB2 or Postgres, then once you add it in /soapui/ext/ folder you need to restart SoapUI.{\Program Files\SmartBear\SoapUI-Pro-5.0.0\bin\ext\}

And that’s how you can get a quick start boost-up for creating new tests in SoapUI.

1 view0 comments
bottom of page