> ## Documentation Index
> Fetch the complete documentation index at: https://docs.maia.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Run Pipeline To Test

export const ComponentMetadata = ({warehouses, unsupportedWarehouses = [], componentType, connectionInputs, connectionOutputs}) => {
  const allWarehouses = [...warehouses.map(w => ({
    name: w,
    supported: true
  })), ...unsupportedWarehouses.map(w => ({
    name: w,
    supported: false
  }))];
  return <div style={{
    background: 'var(--colors-background-light, #f9fafb)',
    border: '1px solid var(--colors-border-default, #e5e7eb)',
    borderRadius: '12px',
    padding: '20px 28px',
    marginBottom: '28px',
    boxShadow: '0 1px 4px rgba(0,0,0,0.10)'
  }}>
      <table style={{
    width: '100%',
    borderCollapse: 'collapse'
  }}>
        <tbody>
          <tr>
            <td style={{
    fontWeight: '600',
    paddingRight: '32px',
    paddingBottom: '14px',
    whiteSpace: 'nowrap',
    verticalAlign: 'middle',
    width: '180px'
  }}>Project Availability</td>
            <td style={{
    paddingBottom: '14px',
    verticalAlign: 'middle'
  }}>
              <div style={{
    display: 'flex',
    flexWrap: 'wrap',
    gap: '8px'
  }}>
                {allWarehouses.map((w, i) => <span key={i} style={{
    background: w.supported ? '#dcfce7' : '#fee2e2',
    color: w.supported ? '#15803d' : '#b91c1c',
    border: `1px solid ${w.supported ? '#bbf7d0' : '#fca5a5'}`,
    borderRadius: '9999px',
    padding: '3px 12px',
    fontSize: '0.85rem',
    fontWeight: '500',
    whiteSpace: 'nowrap'
  }}>
                    {w.name} {w.supported ? '✅' : '❌'}
                  </span>)}
              </div>
            </td>
          </tr>
          <tr>
            <td style={{
    fontWeight: '600',
    paddingRight: '32px',
    paddingBottom: '14px',
    whiteSpace: 'nowrap',
    verticalAlign: 'middle'
  }}>Component Type</td>
            <td style={{
    paddingBottom: '14px',
    verticalAlign: 'middle'
  }}>{componentType}</td>
          </tr>
          <tr>
            <td style={{
    fontWeight: '600',
    paddingRight: '32px',
    paddingBottom: '14px',
    whiteSpace: 'nowrap',
    verticalAlign: 'middle'
  }}>Connection Inputs</td>
            <td style={{
    paddingBottom: '14px',
    verticalAlign: 'middle'
  }}>{connectionInputs}</td>
          </tr>
          <tr>
            <td style={{
    fontWeight: '600',
    paddingRight: '32px',
    whiteSpace: 'nowrap',
    verticalAlign: 'middle'
  }}>Connection Outputs</td>
            <td style={{
    verticalAlign: 'middle'
  }}>{connectionOutputs}</td>
          </tr>
        </tbody>
      </table>
    </div>;
};

<ComponentMetadata warehouses={["Snowflake", "Databricks", "Amazon Redshift", "Google BigQuery"]} componentType="Test" connectionInputs="One" connectionOutputs="Unlimited" />

The **Run Pipeline To Test** test component lets you execute the pipeline being tested. It works in a similar way to the [Run Orchestration](/docs/components/run-orchestration) and [Run Transformation](/docs/components/run-transformation) components, but supports running either type of pipeline.

Any pipeline executed through this component creates an association between the test and the specified pipeline.

<Note>
  This component is only available in [Tests](/docs/components/test-pipelines).
</Note>

***

## Properties

<ResponseField name="Name" type="string" required>
  A human-readable name for the component.
</ResponseField>

{/* <!-- param-start:[pipelineToTest] | warehouses: [snowflake, databricks, redshift, bigquery] --> */}

<ResponseField name="Pipeline to test" type="drop-down" required>
  Choose an existing pipeline to test.
</ResponseField>

{/* <!-- param-start:[setScalarVariables] | warehouses: [snowflake, databricks, redshift, bigquery] --> */}

<ResponseField name="Set scalar variables" type="column editor">
  Pipeline variables declared in the pipeline under test can be given new values through this property. The values set here are used as the new defaults in the pipeline under test when it runs through this property only; they don't change any actual default values which have been set in the pipeline.

  * **Variable:** Select the variable in the pipeline under test that you want to assign a new value to.
  * **Value:** Enter a new value for the variable. Ensure that the new value is of the correct [type](/docs/guides/variables#variable-type).

  Read [Project and pipeline variables](/docs/guides/variables) for more information.

  Click the **Text mode** toggle at the bottom of the dialog to open a multi-line editor that lets you add items in a single block. For more information, read [Text mode](/docs/guides/components-overview#text-mode).

  To use grid variables, toggle **Use Grid Variable** on at the bottom of the dialog. For more information, read [Grid variables](/docs/guides/grid-variables).
</ResponseField>

{/* <!-- param-start:[setGridVariables.variable, setGridVariables.status, setGridVariables.gridValues] | warehouses: [snowflake, databricks, redshift, bigquery] --> */}

<ResponseField name="Set grid variables" type="column editor">
  Grid variables declared in the test with a public scope can be used by the pipeline under test. These variables can be given new values in the pipeline under test through this property. For more information, read [Grid variables](/docs/guides/grid-variables).

  * **Name:** Lists every grid variable in the pipeline under test.
  * **Status:** Defines which values each grid variable will use when the pipeline under test runs. Options are:
    * **Use defaults:** Use the defaults set in the pipeline under test's grid variable when the pipeline under test runs in this component.
    * **Set values:** Lets you assign new values to the pipeline under test's grid variable. The values set here act as temporary defaults only for executions triggered through this property and do not change the actual defaults defined in the pipeline under test.
    * **Use grid:** Select a grid variable from the test and assign its values to the grid variable in the pipeline under test when the pipeline runs in this component. Use the **Column Mapping** drop-downs to map each column in the grid to a column from the test grid. Take care to ensure you are mapping like-for-like data types.
</ResponseField>