Adding Test Suites Through the UI

Test Suites are logical container allowing you to group related Test Cases together from different tables. This is a great way to group related test cases together and set a single alert for test case failure.

You will need to make sure you have the right permission in OpenMetadata to create a test.

Step 1: Creating a Test Suite

From the vertical navigation bar, click on Quality icon > Data Quality and navigate to the By Test Suites tab. From there click on Add Test Suite button on the top right corner.

On the next page, enter the name and description (optional) of your test suite.

Step 2: Add Test Cases

On the next page, you will be able to add existing test cases from different entity to your test suite. This allows you to group together test cases from different entities Note: Test Case name needs to be unique across the whole platform. A warning message will show if your Test Case name is not unique.

Table Test Suites and Bundle Suites

OpenMetadata has two kinds of test suites. They differ in how they get their owners, which matters when you set up permissions.

	Table test suite	Bundle Suite
Created	Automatically, one for each table	By you, as described above
Contains	The test cases of one table	Test cases from any tables
Owners	Taken from the table. To change them, change the owners of the table.	Set on the suite itself.

Because of this, the owner of a table can manage that table’s test suite and test cases without extra setup, while the owner of a Bundle Suite doesn’t get any rights on the tables of the test cases it contains.

Let Owners View and Manage Their Tables’ Tests

By default, OrganizationPolicy-Owner-Rule gives owners full access to the assets they own. For a test case, OpenMetadata checks the owners of the table that the test case belongs to. If you removed or narrowed that rule, use this recipe to let owners view and manage the tests of their own tables:

Go to Settings > Access Control > Policies and click Add Policy. Name it TableOwnerDataQuality.
Add a rule with these settings:
Setting Value
Effect Allow
Resources TestCase, TestSuite
Operations ViewAll, EditAll, Create
Condition isOwner()
Add the policy to a role, and assign the role to your data owners or their team.
Sign in as an owner, open one of their tables, and confirm that they can view, add, and edit its test cases.

Setting	Value
Effect	Allow
Resources	`TestCase`, `TestSuite`
Operations	`ViewAll`, `EditAll`, `Create`
Condition	`isOwner()`

The Permission Debugger doesn’t list the test case and test suite resources. To check these permissions, sign in as the user and try the action. For more information, see Permission Debugger.

Data Quality

Adding Data Quality Test Cases from yaml config

When creating a JSON config for a test workflow the source configuration is very simple.

source:
  type: TestSuite
  serviceName: <your_service_name>
  sourceConfig:
    config:
      type: TestSuite
      entityFullyQualifiedName: <entityFqn>

The only sections you need to modify here are the serviceName (this name needs to be unique) and entityFullyQualifiedName (the entity for which we’ll be executing tests against) keys. Once you have defined your source configuration you’ll need to define te processor configuration.

processor:
  type: "orm-test-runner"
  config:
    forceUpdate: <false|true>
    testCases:
      - name: <testCaseName>
        testDefinitionName: columnValueLengthsToBeBetween
        columnName: <columnName>
        parameterValues:
          - name: minLength
            value: 10
          - name: maxLength
            value: 25
      - name: <testCaseName>
        testDefinitionName: tableRowCountToEqual
        parameterValues:
          - name: value
            value: 10

The processor type should be set to "orm-test-runner". For accepted test definition names and parameter value names refer to the tests page.

Note that while you can define tests directly in this YAML configuration, running the workflow will execute ALL THE TESTS present in the table, regardless of what you are defining in the YAML.This makes it easy for any user to contribute tests via the UI, while maintaining the test execution external.

You can keep your YAML config as simple as follows if the table already has tests.

processor:
  type: "orm-test-runner"
  config: {}

Key reference:

forceUpdate: if the test case exists (base on the test case name) for the entity, implements the strategy to follow when running the test (i.e. whether or not to update parameters)
testCases: list of test cases to add to the entity referenced. Note that we will execute all the tests present in the Table.
name: test case name
testDefinitionName: test definition
columnName: only applies to column test. The name of the column to run the test against
parameterValues: parameter values of the test

The sink and workflowConfig will have the same settings as the ingestion and profiler workflow.

Full `yaml` config example

source:
  type: TestSuite
  serviceName: MyAwesomeTestSuite
  sourceConfig:
    config:
      type: TestSuite
      entityFullyQualifiedName: MySQL.default.openmetadata_db.tag_usage
#     testCases: ["run_only_this_test_case"] # Optional, if not provided all tests will be executed

processor:
  type: "orm-test-runner"
  config:
    forceUpdate: false
    testCases:
      - name: column_value_length_tagFQN
        testDefinitionName: columnValueLengthsToBeBetween
        columnName: tagFQN
        parameterValues:
          - name: minLength
            value: 10
          - name: maxLength
            value: 25
      - name: table_row_count_test
        testDefinitionName: tableRowCountToEqual
        parameterValues:
          - name: value
            value: 10

sink:
  type: metadata-rest
  config: {}
workflowConfig:
  openMetadataServerConfig:
    hostPort: <OpenMetadata host and port>
    authProvider: <OpenMetadata auth provider>

How to Run Tests

To run the tests from the CLI execute the following command

metadata test -c /path/to/my/config.yaml

Data Quality and Observability

Adding test suites through the UI

Adding Test Suites Through the UI

Step 1: Creating a Test Suite

Step 2: Add Test Cases

Table Test Suites and Bundle Suites

Let Owners View and Manage Their Tables’ Tests

Data Quality

Adding Data Quality Test Cases from yaml config

Key reference:

Full `yaml` config example

How to Run Tests

​Adding Test Suites Through the UI

​Step 1: Creating a Test Suite

​Step 2: Add Test Cases

​Table Test Suites and Bundle Suites

​Let Owners View and Manage Their Tables’ Tests

​Data Quality

​Adding Data Quality Test Cases from yaml config

​Key reference:

​Full yaml config example

​How to Run Tests

Adding Test Suites Through the UI

Step 1: Creating a Test Suite

Step 2: Add Test Cases

Table Test Suites and Bundle Suites

Let Owners View and Manage Their Tables’ Tests

Data Quality

Adding Data Quality Test Cases from yaml config

Key reference:

Full `yaml` config example

How to Run Tests