Using Databases in Test Data Automation

Test Data Automation has a rich toolkit of database functions that help you understand, test, mask, synthesise, and mimic your database content, tables, and structures in all common database management systems.

Before you can use a database table in Test Data Automation, it needs to be scanned in, which imports the schema, and a definition needs to be created. The definition is what Test Data Automation uses to later apply database functions.

Definitions are structured packages that can hold and describe any number of versions of a database. Having versions of a file lets Test Data Automation compare and find the differences between versions, and mirror change over time.

Once you have a definition, the Data Activities can mask, compare, subset, clone, generate and analyse your data

This documentation will take you from scanning your database, creating a definition and then creating versions.

In this documentation, we will use these tables:

OT_Contacts, the customer contact table used by Example Corp.

OT_Employees, the table of employees

And a modified version of the OT_Employees file with hierarchy grades. We’ll use this to demonstrate definition version creation.