Pipeline Definitions and Pipeline Runs
In TESTMETRIX®, pipeline definitions describe what type of pipeline is executed.
They serve as reusable templates for recurring test processes.
Typical examples are:
- a Post-Commit Pipeline that is automatically executed after every commit
- a Nightly Pipeline that runs every night
- a Release Pipeline that is started before a release
A pipeline definition is therefore not the actual execution, but the overarching description of the test process.
Why do Pipeline Definitions exist?
In software development, the same types of pipelines are executed over and over again.
Without a dedicated level for these definitions, all runs would be disconnected with no way to group or compare them.
Through pipeline definitions it becomes clear:
- which type of pipeline was executed (that is the pipeline run)
- which test runs belong to the same pipeline
- how results can be compared across multiple runs
This creates structure and improves traceability.
Difference between Pipeline Definition and Pipeline Run
A pipeline definition describes the type or category of a pipeline.
A pipeline run is a concrete execution of this definition.
Example
- Pipeline Definition:
Nightly Pipeline - Pipeline Run:
Nightly Run #123 from 12.04.2026
The definition stays the same while individual runs accumulate over time.
Using Pipeline Definitions and Pipeline Runs
Create Pipeline Definition
Pipeline definitions are typically created once via the user interface.
Since they rarely change, creating them manually via the user interface is the recommended approach.
Create Pipeline Run
A pipeline run represents a concrete execution of a pipeline definition.
It is created before the associated test runs are assigned.
This is particularly useful when:
- multiple test runs belong to a common execution
- tests run on different devices or configurations
- different test levels are to be summarized
Pipeline runs can be created via the user interface or the REST API.
In practice, this is done automatically via the API.
Assigning Test Runs
When uploading test runs, you specify which pipeline run they belong to.
This allows multiple test runs within an execution to be grouped together and analyzed jointly.