Today let us try to understand the different options available in new Test Suite wizard in soapUI.
I shall be referring to Global Weather web service from WEBSERVICEX.NET as an example.
Let us create a new workspace in soapUI and call it as ‘testersforum’.
Create a new project for Global Weather Service as shown below. (For details on creating a new workspace and creating a new project please refer to my earlier posts on soapUI)
Now in the new soapUI Project window make sure to select the check box for Create Test Suite and then click on OK Button as shown above.
Here to have a better understanding let us look at the two different options practically. Since our web service has both soap and soap1.2 bindings, we will be able to create individual test suites for respective bindings.
First Option:
In the Generate Test Suite window select the Style, Request Content and select the operations to be included if there are more than 1 available and then click on OK button.
For SOAP 1.2 binding, let us select ‘One Test Case for each Operation’ as the style and ‘Create new empty requests’ as Request content as shown below.
Now provide the Test Suite name.
We have successfully created a Test Suite with 2 different Test Cases with individual Test Steps per operations as shown below. You should be able to see the below structure once you are done with generating Test Suites for both the bindings.
Second Option:
Now let us select the other options when soapUI prompts to generate Test Suite i.e. both style and request content for the other soap binding as shown below.
Provide the Test Suite name when it prompts for the second Test Suite
Once the Test Suites are created, you should be able to see the below structure where we have a single test case with two Test Steps for two operations.
Based on the above two approaches of Generating Test Suites, the conclusion is if you want to test individual operations separately choose the 1st option and if you want to test it as a scenario choose the second option.
Request Content can be anything either you create new empty request or you can choose the existing request from the interface only if your interface already has some test data defined in its request.
Please don't forget to let me know if this was useful by posting your comments. Happy reading..!! :)
Blogger Labels: Test,Suite,variation,options,Service,Global,Weather,WEBSERVICEX,workspace,Project,wizard,Create,Button,Generate,Style,Request,Content,Here,bindings,option,suites,SOAP,Case,Operation,Cases,Steps,conclusion,scenario,interface,data,soapUI
I shall be referring to Global Weather web service from WEBSERVICEX.NET as an example.
Create a new project for Global Weather Service as shown below. (For details on creating a new workspace and creating a new project please refer to my earlier posts on soapUI)
Now in the new soapUI Project window make sure to select the check box for Create Test Suite and then click on OK Button as shown above.
Here to have a better understanding let us look at the two different options practically. Since our web service has both soap and soap1.2 bindings, we will be able to create individual test suites for respective bindings.
First Option:
In the Generate Test Suite window select the Style, Request Content and select the operations to be included if there are more than 1 available and then click on OK button.
For SOAP 1.2 binding, let us select ‘One Test Case for each Operation’ as the style and ‘Create new empty requests’ as Request content as shown below.
Now provide the Test Suite name.
We have successfully created a Test Suite with 2 different Test Cases with individual Test Steps per operations as shown below. You should be able to see the below structure once you are done with generating Test Suites for both the bindings.
Second Option:
Now let us select the other options when soapUI prompts to generate Test Suite i.e. both style and request content for the other soap binding as shown below.
Provide the Test Suite name when it prompts for the second Test Suite
Once the Test Suites are created, you should be able to see the below structure where we have a single test case with two Test Steps for two operations.
Based on the above two approaches of Generating Test Suites, the conclusion is if you want to test individual operations separately choose the 1st option and if you want to test it as a scenario choose the second option.
Request Content can be anything either you create new empty request or you can choose the existing request from the interface only if your interface already has some test data defined in its request.
Please don't forget to let me know if this was useful by posting your comments. Happy reading..!! :)
del.icio.us Tags: soapUI,Test Suite,Web Service Testing,SOA Testing,Test Cases,Interface Testing,API Testing
Technorati Tags: Test,Suite,variation,options,Service,Global,Weather,WEBSERVICEX,workspace,Project,wizard,Create,Button,Generate,Style,Request,Content,Here,bindings,option,suites,SOAP,Case,Operation,Cases,Steps,conclusion,scenario,interface,data,soapUI, API Testing, SOA Testing, Blogger Labels: Test,Suite,variation,options,Service,Global,Weather,WEBSERVICEX,workspace,Project,wizard,Create,Button,Generate,Style,Request,Content,Here,bindings,option,suites,SOAP,Case,Operation,Cases,Steps,conclusion,scenario,interface,data,soapUI
Generating Test Suites in soapUI
Reviewed by Suntaragali The Smart Techie
on
December 23, 2012
Rating:
Reviewed by Suntaragali The Smart Techie
on
December 23, 2012
Rating:
This blog is truly useful to convey overhauled instructive undertakings over web which is truly examination. I discovered one fruitful case of this truth through this blog. I will utilize such data now. Liquid chromatography mass spectrometry
ReplyDelete