2. Data Driven Testing: Implementation
Now when we have the database set up and a JDBC driver running, let's get going with the Implementation.
Let us first examine what we want to do:
- Get an Amazon User ID from a configuration file
- Retrieve an Author from a MS SQL Database
- Call Amazons ItemSearch with the User ID and Author
- Handle the Response in some way
- Loop until done
All thiz is in the Tutorial .zip.
Step o: Start the project
- First we create a project
from the URL http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl. In this we’ll choose the itemSearch request and add this to a TestCase.
- We can then trim the request down to containing what we want.
<soapenv:Envelope xmlns:soapennv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://webservices.amazon.com/AWSECommerceService/2007-05-14">
or more repetitions:-->
Step 1: Get your ID
Now we have to populate the request with data and the first step is populating the element <ns:SubscriptionId></ns:SubscriptionId>. (Note, if you don’t have a subscription ID for Amazon Web Services, get it now). We get the data by using a configuration file containing just one line;
// SubscriptionID=[your ID] //
and retrieving this in a PropertiesStep. We also have a second property, resultCount, which we’ll use later, more about this later, and a Property named type referring to the type of search we’re doing, i.e. books.
Step 2: Connecting to MS SQL
- Let’s go on to actually populating the request and get to the heart of this tutorial. Let’s add a datasource.
- Then we configure the data source, here are the parameters:
- Please note that you will have to change port, user and password to what you might have in your environment.
- We also will have to add two properties, index and author that corresponds to the SQL Statement. Once done, you can test the entire step.
Connection String: jdbc:sqlserver://localhost:1898;databaseName=db_Author;user=eviware;password=eviware;
SQL Query: SELECT * FROM tb_Author
Step 3: DataTransfer
Now that we have collected the data, let’s transfer it into the request.
Let’s add a PropertyTransfer Step with three transfers, MoveAuthor, MoveMyID, MoveType.We can use the XPath Selector tool to make the transfer a breeze.
We have made a small movie showing this step. Watch it here (in a new window)
Step 4: Check the test
What we have now should look like this.
- Gotten base parameters
- Gotten Test Data
- Transferred into a search
- The Search Request
Step 5: Using the result
Remember we had a property called resultcount, let’s use it. We make another property transfer step that takes the number of hits from the ItemSearch response and moves it to the property, remember to use the xpath selector. Also remember that you have to run the request in order to be able to use the selector, without a proper request you won’t have a proper response to choose from.
Step 6: A Groovy Step
In order to see that this is working, let’s show a dialog with the result. We add a Groovy script containing the following;
// get target step
def step = testRunner.testCase.getTestStepByName( "My ID" );
def step2 = testRunner.testCase.getTestStepByName( "MySQL Retrieve" );
"Got " + step.getPropertyValue( "ResultCount" ) + " hits for author [" +
step2.getPropertyValue( "Author" ) + "]" );
Step 7: Loop it!
Lastly, in order to use all data in the database, we need to finish the test with a DataSourceLoop step.
Now we can run the entire test, and should be receiving the following:
And that is it! You now have a working test! Creating a data driven test in soapUI isn’t harder than that.
But wait! What about MySQL users? Well basically it's the same thing, all you need to do is change the DataSourceStep to the following:
Connection String: jdbc:mysql://localhost:3306/eviware_demo_datainsert?user=evidemo&password=evipass
SQL Query: SELECT * FROM tb_Author
Both MySQL and MS SQL projects are available to Pro Users.
Project Files and More coming up!