Questions about data-driven testing

Currently, you can define a set of inputs for a script, and specify what values they should take.

You can use a JSON file of the format

[
  { key: value, key: value, ... },
  { key: value, key: value, ... },
  ...
]

to specify multiple rows of data, causing Builder to play back the test using each row of data in turn. Data is simply put into playback variables, so the script

print ${foo}

with the JSON file:

[ {"foo": "bar"}, {"foo": "quux"} ]

would run twice, printing "bar" and then "quux".

At this point, I would very much like your input on what features you would like to see for a robust data-driven testing support. Specifically, how would you like to see data-driven tests exported? Should the exported scripts contain code for accessing the data, or should the data be passed during script invocation / in the constructor?

Two things are already definitely planned: support for the XML format used by Selenium IDE data-driven testing, and support for data-driven testing in both the Java-based and node-based Selenium Interpreter.

David Linse3 Mar 2014, 5:08 p.m.Hi there.. This sounds pretty cool. Q: where do i have to put the data for `inputs` ? ```json { "type": "script", "seleniumVersion": "2", "formatVersion": 1, "steps": [ { "type": "get", "url": "http://localhost" }, { "type": "print", "text": "${foo}" } ], "data": { "configs": {}, "source": "none" }, "inputs": [ { "foo": "this is 'foo'" }, { "foo": "this is 'bar'" }, ] } ``` the above script only prints ``` Mar 3, 2014 5:06:07 PM com.sebuilder.interpreter.steptype.Print run INFO: ${foo} ``` regards david

Nishi16 Mar 2015, 12:10 p.m.would like to see option to select the input file at the run time. The choice of data can be changed from exported script as well.