#itko

[vaseem-javed-blog]

(via https://www.youtube.com/watch?v=1DaKmY2WnKY)

[automatedfun-blog]

Low level - highly reusable Lisa test

Low level high reusable Lisa test scenario:

First you want to create a CSV file that contains all of your service information so what you include in there would be your WSDL your XML request and any other necessary parameters 4 your service execution or for the dot net service step that you have parameter-ized.

something like WSDL, XML, endpoint.

CSV File 1 1. WSDL, XML, endpoint 2.http://service.svc?wsdl,SOME XML REQUEST,http://service.

You would create a second CSV file that contains any validation that you want to do so if you are validating a successful response and you know the response you could have simply just one column titled XML and that column would just contain values of the XML responses that you would expect.

CSV File 2 1.XML RESPONSE 2.SOME XML RESPONSE

So the important thing to remember is that your columns and rows should match-up between CSV file 1 and CSV file 2. In other words the data row 1 (Actual row 2) in the CSV file 1 would correspond with Data row 1 (actuall row 2) of CSV file 2.

Now within your LISA test you will have a step for your dot net services that will have all of the values that you passed in parameter-ized. Next you'll want to attach your CSV files. To do that select a data set and use the the delimited data file data set. if you associate both CSV files you'll be able to pull the values from both files.

Next you want to set a looping statement for your for your CSV file. So in your dot net step what you want to do is open it up and you should see a dropdown for when the status is completed, by default it will be set to end the test. Instead of having end the test, you want to set it to go back to the step you just creating a loop with the Lisa test. If you have multiple lines within your data set it will iterate through all of your data and when he gets completed then it will exit out of your test.

You will want to make sure that your data sets are set to end the test when they reach the end otherwise you'll create an infinite loop and your test will never properly end.

Now the downside to doing this is that you're going to have one test run for every scenario but as I said this is a high level framework that allows for re-usability and gives you the ability to run multiple scenarios why only using a single test.