I figured it out, and in hindsight it was pretty simple.
The syntax looks like this:
"KeywordTests.Test_Name.Variables.DDL_Data["textboxClientName"]"
You'll need to make the variables into project variables instead of local variables. That way the keyword test can write to them and then the script can read from them.
I don't see a process in that document that details how to convert and/or create Data Driven Loop variables as Project level variables. I have read most of the support documentation and what I have found on Google and I still can't figure out the best route. Is this possible?
Maybe I am not being clear on what I am trying to accomplish.
Data Driven Loops in Keyword Tests create Local Variables in a project (my example in the attachment) for each column and the data within each row of a column. I want to take these variables and compare them to variables in a separate Script Routine (Python). Currently, I am unable to make this work because they are all considerd "Local" to the Keyword test. I have read all of the attached support documents and cannot find how to take the variables created from a DDL and compare them in a separate test.
Thanks for your help! Any advice or best practice suggestions are appreciated.
vondie
I see the confusion. "Local Variables" is being used two different ways. The variables being used to reference the DDT data are not accessible outside the loop. Other variables can be defined for use inside the whole keyword test (local variables) or the whole project (project variables).
What does the script routine need to accomplish? Can you not put it inside the loop? That way you would have each set of data accessible as the loop progresses.
