In this section:
Hierarchical data sets are added to TDA when transactions are recorded and added to the database during testing. You can review and interact with the data so that it can be used across testing scenarios.
See About the Data Repository for definitions of terms used in this section.
The main application toolbar contains functionality associated with the data repository, but additional functionality may appear in the toolbar depending on the current view.
You can perform the following actions in the main toolbar.
Click on a repository in the Data tab to open the data repository view.
You can perform the following actions in the data repository view.
The data set will be added to the repository page. See Adding and Modifying Data for next steps.
You can also create a data set on import.
You can download the data set or record type as a JSON file.
Choose Delete from the ellipses menu and confirm that you want to remove the data set or record type when prompted. If the data set contains record types that do not reference or are not referenced by another component, you can enable the Delete orphaned record types option to ensure that the data set is completely removed. This option does not apply to record types.
Click on a data set in the Data Sets column to open the Data Record View.
The data record view is the interface for modifying data. Click on a data set from the data repository view to access records.
You can perform the following actions.
Click on the ellipsis menu in the data set header to add key columns, value columns, and to add first and last rows.
New value columns are always added to the end of the table.
Click on the column actions menu to rename or delete the column. You can also sort how the data is presented by key column values. Sorting does not affect the structure of the data.
Click the row actions menu to add an inline row, duplicate the data row, or delete the row.
You can expand rows to view the data in the JSON viewer.
Null and exclude are special values in TDA and are displayed differently.
If a primitive field was configured to be set to null/exclude, it is represented as [null] / [exclude]. For example, see Age in the screenshot below.
If a primitive list field is set to null/exclude, it is presented as an array of one item with the value [null] / [exclude]. For example, see key in the screenshot below.
If a record list field is set to null/exclude, it is presented as an array of one item with the value [null record] / [exclude record] (to distinguish it from a null/exclude primitive list). For example, see string in the screenshot below.
If you want to set a field to null or exclude (so it will not appear in the message when an element is populated from this data source), use [null] or [exclude] while editing.
Click Edit to make values editable.
If the repository is locked by another user, you will not be able to modify it or delete any of its records. |
Editable values will become active. You can edit data key values in the table and primitive values in the JSON view editor.
Click Save when finished.
Only CSV and CSV-formatted files are currently supported for import.
(Optional) Configure how the data is imported. Click in a field in the File options and choose from the available settings. Enable the Trim spaces option to remove extraneous spaces from the data. You can designate a field as a key, value, or both. Keys enable message responders to find the correct row of data to construct responses.
