Data validation testing is a process to check whether a set of data is valid and complete. Data Validation test cases test the accuracy and validity of the data by selecting and comparing two data sets.
When you create a test case, you select the connections that contain the data to compare, the data sources to compare, and the columns to compare. The data sources can be database tables, views, or saved SQL queries. Data Validation maps the columns in the two data sources. If any column remains unmapped, you can map it manually.
You can also choose to compare the entire table based on the actual data values or use aggregation functions to compare the table.
Optionally, you can configure the following options:
Bad record limit
You can define the maximum number of unmatched, extra, and missing records to show in the detailed test results.
String validation
You can specify whether you want to ignore casing differences in the data and trim leading and trailing white spaces in string values.
Data sampling level
You can configure data sampling for Data Validation to compare between source and target data. The less data that Data Validation samples, the faster the test runs. This setting applies to all the columns you select to compare, in both tables.
Schedule
You can select a schedule to run the test case. Create schedules in Administrator.
Email notifications
You can specify whether you want to send email notifications when the test case completes successfully or fails. You can either use the default email notification options that are configured in Administrator or define custom email notifications. When you use custom email notifications, you can specify the email addresses that Data Validation must use for the success and failure email notifications. Separate multiple email addresses with a comma.
Logging level
You can configure a test case to use one of the following logging levels:
- Standard. The log includes error messages.
- Verbose. The log includes messages of all logging levels. This option is useful for debugging.
Before you run test cases, verify that the Secure Agent that runs them has a minimum of 32 GB memory.
When you run the test case, Data Validation compares each column in the source with the column in the target that is mapped to it and reports whether or not the two data sets match. For unmatched data sets, the report lists unmatched, missing, and extra records.