Use test case reports to view data about test case connections, sources, and jobs. Use test suite reports to view the most recent job reports for multiple test cases.
Each time you run a test case, Data Validation creates a test case job. Data Validation adds numbers in ascending order to the name of the test case to create unique job names. Data Validation generates a report for each successful job run.
The report shows the general details of the job, sampling data, total records, match results, row count, and column matching status. The row count and the column matching status show the data type, precision, and scale for each row. You can download a report of successful jobs.
The data type match result shows whether the data types of the columns compared in both connection tables match. Data Validation removes trailing zeros from decimal data types to prevent matching errors when comparing table columns.
The report shows details about the missing, unmatched, and extra records in the job. Data Validation shows 100 rows of data for each report.
When you create a test case, you select the location where Data Validation saves the reports. Data Validation stores the 10 most recent reports and purges the oldest reports. Data Validation purges detailed reports after the time period that you configure on the Secure Agent. The default time period is seven days.
Viewing a job report
You can view job reports on the job report page. You can open the job report page from the test case details page or from a test suite.
1To open a job report from the test case details page, perform the following tasks:
- On the Recent Test Cases panel of the Home page , or on the Explore page, click a test case.
The test case details page opens.
- On the test case details page, select the Jobs tab and navigate to the row that contains the test case job. On the Report column, click View.
The report page opens.
2To open a job report from a test suite, perform the following tasks:
- On the Explore page, click a test suite.
- Click the Test Suite Report tab.
Data Validation generates a test suite report that displays the most recent test case jobs.
- Navigate to the row that contains the test case job. On the Report column, click View.
The report page opens.
3In the Column Matching Status area, select See data type match result.
The data type match results appear. The following image shows the report page of a test case job with the data type match results:
4Expand the Detailed Report area to view data of missing, unmatched, and extra records in the job results.
The following image shows the Unmatched Records tab in the Detailed Report area of the report page:
Note: If the tables that you compare contain duplicate records, Data Validation includes the duplicate records in the matched records count.
Downloading a successful job report
You can download a report of successful jobs from the test case details page to a Microsoft Excel file.
1On the Explore page, click a test case.
The test case details page opens.
2On the test case details page, select the Jobs tab and then navigate to the row that contains the test case job. On the Report column, click View.
The report page opens.
3Click the download icon to the right of the job report.
The report is downloaded to your machine.
Rules and guidelines for data validation
Consider the following rules and guidelines for data validation:
•When you compare data types across databases, if the corresponding Informatica native type differs in precision compared to the databases, you might see a mismatch.
•If you compare a binary data type with data types such as string or decimal, you might see a mismatch.
•When you compare the time data type across databases, you might see a mismatch because Informatica treats time as datetime and each database has a different default date.
•Informatica treats the datetimeoffset data type as varchar (0). If you compare datetimeoffset values with datetime values, you might see a mismatch.
•When you compare floating point data types across databases, the default exponential notation on each database might be different. You might see a mismatch in the case of large floating point numbers.
•When you compare data between Oracle and Snowflake databases, if the Oracle database contains varchar data, you might see a mismatch. To prevent this issue, map Oracle varchar data to nvarchar2.
•If an Oracle table stores Unicode data in an nvarchar column and you map the column to other databases with Unicode data, you might see a mismatch. The mismatch occurs because Oracle supports Unicode data only in its nvarchar2 data type.
