Using Data Files in Enterprise Test Data
Using Data Files in Enterprise Test Data
Article summary
Did you find this summary helpful?
Thank you for your feedback
Before you can leverage a data file in Enterprise Test Data it must first be scanned to generate a file schema, followed by the creation of a definition. A definition equips Enterprise Test Data with the necessary information to utilize the file in a Test Data Activity.
Definitions are structured packages that can hold and describe any number of versions of a data file. This versioning feature allows Quality Modeller to discern differences between file versions and track alterations over time.
The file scanning process generates metadata that allows for the analysis of data patterns, comparison of characteristics sets, and identification of data coverage. This information enables you to deploy a Definition in a Test Data Activity enabling the creation of coverage focused synthetic data to shape test messages and files to align with your testing environment. This process also allows for data file masking, effectively eliminating personally identifiable information, consequently reducing potential breaches of information security regulations. Furthermore, it empowers you to enrich files and messages with complex synthetic data generation functions to embed business logic.
This documentation will take you from scanning your data file, creating a definition and then creating versions.
We will use the following documents throughout:
OT_Contacts.csv contains the customer contact file used by Example Corp.
OT_Employees.csv, the file of employees:
OT_Employees.json and OT_Employees.xml versions:
And OT_Employees with Grade.csv, a new version of the OT_Employees file with hierarchy grades. We’ll use this to demonstrate definition version creation.
