Thanks ChrisAdams. Based on what you said - it looks like I'm on the right track.
This is what I have atm.
This is what my data source grid looks like:
My original question was: "how to do STORE values in the groovy step into data source grid?" Is this possible? If so - then I will add another property in the data source grid called currentDate.
Then I hope to loop the groovy script to get and store date and the api step will 'get data' from the respective property from the datasource grid. Alternatively if I cannot store in data source grid - then I will store in test case properties.
I might be misunderstanding your requirement, but I thought I'd achieved what you originally asked for. My example above uses a Datasource Grid with some static values as well as pulling in values from a Groovy script step.
In the Datasource Grid, the static values will always be there and the values from the Groovy script will be refreshed every run.
In your last reply, you mentioned....
My original question was:"how to do STORE values in the groovy step into data source grid?" Is this possible? If so - then I will add another property in the data source grid called currentDate.
If you look back at my Datasource Grid screenshot, The column for Prop3 shows how the result of the Get Date Groovy script is called.
E.g. with updated screenshot.... Note column three contains... ${Get Date - Groovy Script#result}. When ReadyAPI iterates through the Datasource Grid, it calls Get Date for each row.
Again in the Datasource Grid, you can click the preview to show this....
In your Test flow, you have the Groovy script after the Datasource Grid step. For my approach, the Groovy must come before any step that references it.
To reference the date value from the Datasource Grid in your API step, you can use the $ syntax. E.g.
Alternatively, you can still just pull Current Date directly into you API step without getting it from the Datasource Grid by using ${Get Date - Groovy Script#result}
If I have misunderstood, then let me know and I'll delete this reply.