Forum Discussion

mu123's avatar
mu123
Occasional Contributor
3 years ago

Iterating through Data source values and verifying the matched value

This is the scenario that I am trying to test:  1. I have a REST API step that returns number of ids and names for locations. (Sometimes zero records are returned, sometimes one and sometimes multip...
Data-Driven Testing
Function Tests
REST
  • ChrisAdams's avatar
    ChrisAdams
    3 years ago

    Hi,

     

    You're over-thinking this.  The solution is much easier and you're not far off.

     

    Data-driven tests that use a Datasource step need a Datasource Loop step.  This handles the iteration of the data set.  Steps in between the Datasource and Datasource Loop are called for each row in the data source.

     

    Using your screen shot as a guide, here's what I think you should be moving towards....

     

     

    Note the Data Source Loop step and how Ready API indicates the loop with the arrow.

     

    When you add the Data Source Loop step, you have to configure it.  Here's how I did mine for your example...

    The first value is the link to the data source of interest.  The second value is the first step inside the loop that you want to call.

     

    Before moving onto the Groovy step, it's worth looking at the Datasource.  Again, I borrow from your example...

     

    These properties are accessible within the loop and contains the values for the current row in the datasource.  Without the loop step, you always get the last row.

     

    Ok, Groovy script and how to access the current values....

    Here is the content of the "Let's log stuff - Groovy script' step.

     

     

    You can type all this in, but now is a good opportunity to mention "Get Data".  In your Groovy Step, if you right-click, there is an option called Get Data.  If you click this, you can navigate to the Datasource step and select the value of interest without typing.

     

    You'll notice I added an additional step call "REST Request to call in each iteration".  You can apply the same Get Data idea.  If you want to call another service for each id in your datasource, then instead of calling with a hard-coded value, again right click where the param needs to use get data.  E.g.

     

     

     

     

     

     

mu123's avatar
mu123
Occasional Contributor
3 years ago

I changed the start row to null, end row to null, and Rows per iteration to null. Now the script works.

Thank you all for the suggestions.

  • fgimenes's avatar
    fgimenes
    Occasional Contributor
    2 years ago

    Hi mu123 , would you mind sharing your final script? I am trying a similar implementation and I haven't figured out how to advance the data source to the next line. I am not able to make the data source to go to the next line. It always prints the same value. I am not if it's because my Data Source is in another Test Suite??. This is my code:

     

    def tStep = testRunner.testCase.testSuite.project.testSuites["Innitialization"].testCases["Test Data Setup"].getTestStepByName("Data Source for Registration")
def data = tStep.getDataSource()

//run the datasource test step
data.prepare(testRunner,context,data.getPreparedProperties() )
tStep.run(testRunner,context)

//loop through the datasource to find number of rows
def cnt = 1
while(data.isExhausted() == false) {
	data.next(testRunner,context,data.getPreparedProperties() )
	def MIP = context.expand( '${#[Innitialization#Test Data Setup#Data Source for Registration]#MIP}' )
	def IS_CMA_ACCOUNT_CREATED = context.expand( '${#[Innitialization#Test Data Setup#Data Source for Registration]#IS_CMA_ACCOUNT_CREATED}' )
	def mobileNumber = context.expand( '${#[Innitialization#Test Data Setup#Data Source for Registration]#mobileNumber}' )
	
	log.info("MIP: " + MIP)
	log.info("IS_CMA_ACCOUNT_CREATED: " + IS_CMA_ACCOUNT_CREATED)
	log.info("mobileNumber: " + mobileNumber)
	cnt++
}
log.info("Number of rows in the datasource is: " + cnt)