Data driven

Test cases can be treated as data driven, by adding a data table to them. This enables the parameterized execution of test cases, mainly used when test cases have the same flow, but only differ in input data and expected outcome.

A data driven run can be added, by adding a new data driven run to a data driven table. A new row will be added to the table, requiring a data run name (first column) and at least one data field.

An example; multiple rows of data driven runs
 calculationexpected outcome
Multiplication82 * 211722
Addition22 + 100122
Subtracting19 – 127

Each data field will be usable like a variable in your test steps. So based on the example, you are able to use the ${calculation} and ${expected outcome} in our test steps and JOSF will use the values from the data driven table.

Next to the data fields and the run name, you can toggle the activation of that row by a checkbox. This is handy, when you’d like to execute a certain data row, but this toggle is ignored during playbook runs. Playbook runs always execute all of the runs in a data driven table.

Data driven tables can be referenced and edited from test cases. There’s also a dedicated page to manage data driven tables, by opening the “Data Storage” from the JOSF menu.

Note that – when executed during a playbook run – test case names will be prefixed by the data driven run name.

In this document