We discussed about the test design for Web Services and reviewed a reusable test suite template for designing tests for Web Services in blog #2, let us see how to configure the re-usable framework solution and running the tests in this blog.

To start with, we should create a copy of the base Soap UI re-usable project developed as part of the Framework to test the identified web services. The basic understanding of the framework and its components is a must to configure and use this framework. We already had a brief introduction about the framework architecture in my first blog and also had detailed discussion about test design using the test suite template in previous blog.

Let us get into configuring the tests. There are few configuration properties defined at Soap UI project test suite level. Specifying appropriate values to the properties should be the step 1 in configuring the project. Find below few sample properties.

Test Suite Properties

The values specified for these properties are referred within the test steps (Groovy). The properties at test suite level are static and should be set with appropriate values. To make it more user friendly and ease of use, most of the property values are made standard so that the user can just re-use them in all configured projects without having to change all the property values.

The next set of properties which are run-time properties are defined at Soap UI project test case level.

Run Time Properties

These properties value need not be set by the user.  The framework defines a place holder for dynamic values that will be generated run-time and used within the scripts.

Code Snippet accessing these properties in the script

Code Snippet Properties


Once the test suite is ready with well drafted test cases and the base project is configured with appropriate property values, we are all set to run the tests and validate the web service. Click the “Run” button at test suite level, the framework will execute as configured and designed, validates the web service and generates execution logs, test results and html reports.

In order to make the blogs simple and precise, covering a specific topic I will add more details about logs, test results, html reports and email notifications in blog #4 which will be posted next week. Thanks for following the blogs and I appreciate any feedback, inputs and comments. Thanks all, keep reading.

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>