​

Create Quality Test Cases

​

How to Create a Test

1. Go to the table you want to test and click the Data Observability tab.
2. Click Add Test.
3. Select a Table, Column, or Dimension level test.
4. Enter the test details. See Table Level Test, Column Level Test, and Dimension Level Test for the fields of each level.
5. Click Create to save the test.

​

Table Level Test

• Name: A name that describes your test case.
• Test Type: The validation to run. The fields below it depend on the test type.
• Description: What the test validates.

• Table Column Count to be Between: Define the Min. and Max.
• Table Column Count to Equal: Define a number.
• Table Column Name to Exist: Define a column name.
• Table Column Names to Match Set: Add comma separated column names to match. Also verify whether the column names are in order.
• Custom SQL Query: Define a SQL expression. Select a strategy if it should apply for Rows or for Count. Define a threshold to determine if the test passes or fails.
• Table Row Count to be Between: Define the Min. and Max.
• Table Row Count to Equal: Define a number.
• Table Row Inserted Count to be Between: Define the Min. and Max. row count. This test will work for columns whose values are of the type Timestamp, Date, and Date Time field. Specify the range type in terms of Hour, Day, Month, or Year. Define the interval based on the range type selected.
• Compare 2 Tables for Differences: Compare 2 tables for differences. Checks integrity between the two tables.

​

Column Level Test

• Column: The column to test. A summary of the column appears next to the form.
• Name: A name that describes your test case.
• Test Type: The validation to run. The fields below it depend on the test type.
• Description: What the test validates.

• Column Value Lengths to be Between: Define the Min. and Max.
• Column Value Max. to be Between: Define the Min. and Max.
• Column Value Mean to be Between: Define the Min. and Max.
• Column Value Median to be Between: Define the Min. and Max.
• Column Value Min. to be Between: Define the Min. and Max.
• Column Values Missing Count: Define the number of missing values. Also match all null and empty values as missing. Also configure additional missing strings like N/A.
• Column Values Sum to be Between: Define the Min. and Max.
• Column Value Std Dev to be Between: Define the Min. and Max.
• Column Values to be Between: Define the Min. and Max.
• Column Values to be in Set: Add an array of allowed values.
• Column Values to be Not in Set: Add an array of forbidden values.
• Column Values to be Not Null
• Column Values to be Unique
• Column Values to Match Regex Pattern: Define the regular expression that the column entries should match.
• Column Values to Not Match Regex: Define the regular expression that the column entries should not match.
• Column Values To Be At Expected Location: Define a geographic area, such as a radius around an expected location, that latitude and longitude values must fall within.

​

Set a Failure Threshold (Optional)

1. In Select Test Type, pick a test, for example Column Values To Be Not Null.
2. In Failure Threshold, enter the number of failures to tolerate. It can’t be negative.
3. In Threshold Unit, choose how the threshold is measured:
   • rows: a count of failing rows. In the API this is ABSOLUTE.
   • % of rows: a share of the rows evaluated. For row-level tests the value can’t be higher than 100. In the API this is PERCENTAGE.
   
4. Check the Preview. It restates your choice, for example “Fail when more than 0 row(s) in column fail this test.” A second line shows what the check is measured on, for example “Measured on the 100% sample this table is profiled with.”
5. Optional: Turn on Compute Row Count.
6. Confirm the Data Quality Dimension.
7. Enter a name.
8. Click Create.

• Row-level tests count the rows that break the rule. They fail when that count, or its share of the evaluated rows, is above the threshold.
• Statistical tests widen the accepted bounds by the threshold, so small deviations don’t fail the test.

• Column Values to be in Set rejects a non-zero threshold when its matchEnum option is off, because that mode has no failing rows to tolerate. A threshold of 0 is always accepted.
• Custom SQL Query has its own Threshold and Operator. Its threshold is a value that the query result is compared with, not a number of failures to tolerate. The form adds only a Threshold Unit field.

​

Tests That Support a Failure Threshold

Table Level Tests

Column Level Tests

​

Dimension Level Test

​

View Test Results

​

Filter Test Cases by Status

1. Click Status.
2. Select one or more of Aborted, Failed, Queued, and Success.
3. Click Apply. The button shows how many statuses you selected, for example Apply (2).

​

Open Test Cases From the Summary Tab

• Healthy: Success and Queued.
• Unhealthy: Failed and Aborted.

​

Review Result History

• Last run:
  • The latest status and a message with the measured value and the expected range.
  • The Result / Expected values.
  • The run time and when the next run is due, or Not Scheduled.
• Result history: a chart of the measured value over time. The caption shows what is measured and what it is compared against, for example “Column count vs. allowed range 2–10”. A dashed line marks the allowed limit.
• Configuration, Description, Test Suites, Tags, Glossary Term, and Data Products panels beside the chart.

1. Click the date range on the Result history card. By default it covers the last 30 days and ends today.
2. Choose a time range in one of two ways:
   • Select a preset: Today, Yesterday, This week, Last week, This month, Last month, This year, Last year, or All time.
   • Pick start and end dates on the calendars, or type them in the date fields.
3. Click Apply.

​

Review Run Details

​

Set Up a Pipeline

1. Open the test suite and click the Pipeline tab.
2. Click Add Pipeline. The Add Ingestion form opens, titled Scheduler for Test Cases.
3. In Name, enter a name for the pipeline.
4. Under Scheduler for Test Cases, choose how the pipeline runs:
   • Schedule: the test cases run repeatedly on your schedule.
   • On Demand: the test cases run once, when you start them.
5. For Schedule, choose a Frequency: Hourly, Daily, Weekly, Monthly, or Custom.
6. Set the Time. A line below it summarizes the result, for example “Test Cases scheduled to run At 12:00 AM, every day”. The time zone is UTC.
7. Optional: Turn on Enable Debug Log to capture detailed logs.
8. Optional: Turn off Raise on Error, which is on by default and stops the run when an error occurs.
9. Choose the test cases to run:
   • Turn on Select All Test Cases to run every test case in the suite.
   • Or leave it off and select test cases in the Test case list. Use Search Test Cases and the Status, Test Type, and Column filters to find them. The list shows how many you have selected.
   
10. Click Submit.

​

Handle Test Failures

1. In the Status column, click the status icon of the failed test.
2. Select a test Status.
3. If you mark the test as Resolved, you must give a Reason for the failure and add a Comment. The reasons are Duplicates, False Positive, Missing Data, Other, or Out of Bounds.
4. Click Submit.

​

Delete and Restore a Test Case

1. Navigate to Observability > Data Quality, and click Test Cases.
2. Find the test case and open its row actions menu, then select Delete.
3. The Delete “<name>” Test Case dialog offers two options:
   • Soft Delete (selected by default): Turn off this test case. Restore it later.
   • Permanently Delete: Delete this test case and all its metadata forever. This can’t be undone.
   Choose Soft Delete and click Delete to keep the test case’s execution history and results while turning it off.
4. Toggle Show Deleted on the Test Cases page to find soft-deleted test cases.
5. Open the row actions menu on a deleted test case and select Restore, then confirm. The test case becomes editable and resumes on its existing schedule with its history intact.