Skip to main content
You can run automated tests on your pipelines to catch broken logic or bad output before it reaches production. You create a test by using the Designer canvas and adding components—such as assert and compare components—that let you check the outputs and behavior of the pipeline you want to test. Some key benefits of creating tests for your pipelines are:
  • Regression protection: After you change a pipeline (for example with new logic, a schema change, or a component upgrade), a test re-runs the pipeline and checks that the results still match what you expect. The test can identify cases where a change unexpectedly alters the pipeline output.
  • Testing without touching real data: A test can create an isolated test schema, load mock data with known values, run the pipeline under test, assert on the results (for example, row count, output schema, and specific values), and then drop the schema. The original pipeline and data stays untouched.
  • Baseline comparison: You can use a test to compare against baseline data for incremental pipelines. This helps separate intentional logic changes from unexpected failures.
  • CI/CD: Tests can plug into existing CI/CD workflows, so a failing test can stop a bad change before release.
Any pipeline can have multiple tests associated with it, allowing you to check different functions and scenarios for the pipeline.
You can create tests manually as described on this page, but we recommend using Maia Team to generate them automatically. Prompt Maia Team with Create a test for <pipeline name>, and Maia Team will ask you some questions about what you want to achieve, then generate a test with logical defaults and test data. You can edit the resulting test to customize it further. Read Maia Team overview for details.
Expand this box to watch our video about Test Pipelines in Maia.



Tests panel

The Tests panel lists all tests associated with a pipeline and lets you manage and run the tests. To open the Tests panel, click the Tests tab at the bottom of the Designer canvas when you have a pipeline open. From here you can:
  • Run a single test. Click the run icon next to the test you want to run.
  • Edit a test. Click the … (more options) menu for the test, then click Edit. This opens the test on the canvas.
  • Delete a test. Click the … (more options) menu for the test, then click Delete.
  • Run all tests for the current pipeline. Click Run all tests. Results appear in the panel once each test completes. Tests run sequentially.
  • Create a new test. Click the + icon. This opens the Add test dialog.

Creating a test

Tests are created on the canvas in the same way as an orchestration pipeline, and appear as pipelines in the Files panel. Many components available to orchestration pipelines are also available in tests. In addition, a set of dedicated test components—such as assert and compare components—are available exclusively to tests. These components let you check the outputs of the pipeline to test. Available components are summarized below. You can create a test from the Tests panel of the pipeline you want to test, or from the Files panel.

From the Tests panel

  1. Open the pipeline you want to test.
  2. Click the Tests tab at the bottom of the canvas.
  3. Click the + icon. The Add test dialog opens.
  4. Complete the following properties in the dialog:
    • Test name: A name for the test.
    • Target pipeline: This is pre-filled with the current pipeline and can’t be edited.
    • Folder: The folder in which to save the test. The folder must already exist in the Files panel. Select the folder from the drop-down.
    • Description: An optional description of the test. Limited to 1000 characters.
  5. Click Add.

From a file in the Files panel

  1. In the Files panel, locate the pipeline you want to test.
  2. Click the … (more options) menu next to the pipeline, then click Add test. The Add test dialog opens.
  3. Complete the dialog properties as described above. The Target pipeline field is pre-filled with the pipeline you selected.
  4. Click Add.

From a folder in the Files panel

  1. In the Files panel, click the … (more options) menu next to any folder name, then click Add → Test. The Add test dialog opens.
  2. Complete the dialog properties as described above. For Target pipeline, use the drop-down to select a pipeline. If you have a pipeline open on the canvas, that pipeline is the default selection, but you can select any other pipeline in the folder.
  3. Click Add.
In each case, Designer opens a new test on the canvas, pre-populated with a test template.
A test has an implicit link to the pipeline it’s testing, based on the pipeline named in the “Run Pipeline To Test” component.For this reason, each test is stored by default in the same folder as the pipeline it tests, but you can select a different folder if you wish. For example, it may suit your folder plan for you to put all tests in a dedicated folder. The test will be linked to the original target pipeline regardless of where you save it.

Test structure

When you create a test manually (not through Maia Team), Designer loads a template containing a set of pre-configured components and pipeline variables. This template isn’t a complete, functioning test—it’s intended as a starting point for you to add components to set up your test data and assert the expected results. The template establishes the following general structure:
  1. Set up a test schema: Creates a temporary schema in your cloud data warehouse to isolate the test from your production data.
  2. Set up input data: Populates the test schema with the tables and data required by the pipeline to test.
  3. Run the pipeline to test: Executes the pipeline you are testing.
  4. Assert the results: Checks that the pipeline produced the expected output.
  5. Tear down the test schema: Drops the test schema, removing all temporary data.
For example, if your pipeline simply creates a table, the test could create a test schema, run the pipeline, and then check that the table was created with the correct values. Once the test finishes, the test schema is dropped.

Test schema

The test schema is a temporary schema created in your cloud data warehouse specifically for the test run. It allows you to run tests in isolation without affecting your production data. The template uses the SQL Script component (labeled as Create Test Schema on the canvas) to create the test schema. It also creates some pre-configured pipeline variables—for example, test_database and test_schema—that reference this schema. Use these variables throughout your test wherever you need to refer to the test schema. You can edit the default values of these variables if required.
You can run tests against your production schema, but we recommend using a test schema to avoid any risk to your production data.

Input data

After the schema is created, populate it with the tables and data needed by the pipeline to test. You can use components such as:
  • Create Table From Values: Creates a table directly from values you enter in the component.
  • SQL Script: Executes SQL statements to create and populate tables.
  • Zero Copy Clone: (Snowflake only) Clones an existing schema, providing a fast way to create a copy of production data for testing.

Running the pipeline to test

Use the Run Pipeline To Test component to execute the pipeline you are testing. This component runs the target pipeline to completion before the test continues. The target pipeline runs within the context of the test schema, so it reads from and writes to the temporary tables you have set up.

Asserting results

After the pipeline to test has run, use assert or compare components to verify the results. The following test components are available for this purpose:
  • Assert Table: Confirms that a specified table exists.
  • Assert Table Values: Checks that a table contains the expected values.
  • Assert External Table: Confirms that an external table has been correctly created.
  • Assert Scalar Variables: Verifies that a variable holds the expected value.
  • Compare Table Values: Checks that two tables contain identical values. This is useful if your pipeline creates a table and you want to verify it against a separately defined expected-results table.

Available components

Tests support a subset of orchestration pipeline components, as well as some components that are available exclusively to tests.

Dedicated test components

Available orchestration components