Embedding test data
Concrete test data is often required to execute a test case, e.g.:
- user name
- e-mail address
- password
- etc.In general, test instructions with lists can be used, such as e.g.:
Log into the web shop using the
username "(showcase, showNord, j2ee)"
and the password "(show, show, j2ee)".Nevertheless, the username "j2ee" can sometimes be combined with the "show" password thus rendering it impossible to log into a system to be tested.
However, if different values in a test step or through a test step are dependent upon one another, LF‑ET offers the possibility to embed test data sets that guarantee that ultimately, all values generated in a test case match one another.
In LF‑ET, decision tables can be linked to text files that contain predefined test data in CSV (Comma Separated values) form.
Tip: When the number of values for enumeration is too large, distribution of enumeration in a CSV file is a possible solution.
GTD stands for "global test data" and is used in files and test instructions with a preceding asterisk: *GTD. The case of the letters is irrelevant.
| In order for the area "Embed and filter test data“ in the test instruction editor to be able to be unfolded, a link must be established to a test instruction subgroup for embedding and filtering of test data. |