SoapUI is an open source application for web service testing in a service-oriented architecture (SOA). Its features include web service inspection, invocation, development, simulation, mocking, functional testing, load testing and compliance testing. A commercial version, SoapUI Pro, which focuses mainly on features designed to improve productivity, has also been developed by eviware software. In 2011, eviware was acquired by SmartBear Software.

SoapUI was first published in September 2005 under the GNU General Public License. Since its publication, SoapUI has been downloaded more than 2 million times. It is entirely based on the Java platform and uses Swing for the user interface. This means that SoapUI is multiplatform. SoapUI now supports IDEA, Eclipse and NetBeans.

Basic features include:

  • Inspection of web services,
  • Invocation of web services,
  • Development of web services,
  • Simulation and mocking of web services,
  • Functional testing, load testing, compliance and web services security.

SoapUI is a very extensive tool though, and sometimes it takes some time to understand it in its entirety. Here are 8 very basic tips on how to use SoapUI; following them might not necessary make you a better tester, but it will make you a more proficient user, and that’s a good first step.

  1. Right Click on any item you would like to interact with and see what shows up.
  2. You have a group of tests, called TestSuites that contains the actual tests, called TestCases. A TestCase can in its turn contain a number of steps, called TestSteps. If you follow the TestSuite, TestCase, TestStep structure you have so much to gain. Test reuse is easier; you can clone or copy tests as well as refer to them from other tests.
  3. When you create a new TestCase SoapUI offers an easy name for you, for example “TestSuite for validating Pinscher Testing Updates work” instead of “TestSuite 44”. A good advice is also using the same way of naming Items in your project.
  4. Testing in SoapUI is all about the assertions. Without them you can’t properly say that you have performed a test. Creating assertions is real simple in SoapUI; you create them by going to the Assertion Tab in the SoapUI request/response editor.
  5. Property Transfer is obviously useful to take a value in a response and move it to a request.
  6. When you’ve done the tests, you can see the results, step by step, by looking in the Test Log.
  7. There are a number of logs in SoapUI telling you what might be wrong.
  8. Load testing? Just right click a Functional Test, choose New LoadTest and you’re ready to go!

SoapUI site

Happy Service Testing!:)


share me!:))Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this page