Test Step
- Erick Jones
- Jay-Ar Brouillard
- Ben Hoffman
The Test step executes all Test Sets defined for the given project in the snapshot (or the release for Utility projects) according to the project's defined strategy. Â The specified project must be in the release.
Field | Description |
|---|---|
Step Name | The name of the step. |
Description | An optional description for the step. |
Project Name | The name of the project in the snapshot (or release for Utility projects) to execute tests for (according to its strategy). Â This project must be in the snapshot/release, or the step will fail. |
Test Type | Identifies which types of tests to execute. If not specified, all test types will be executed.  Optionally, use a Groovy expression to make this field dynamic based on some contextual value (e.g. a property defined on the pipeline, and specified on the release). |
Precondition | An optional Groovy script which determines whether the gate or step is applicable during execution. The script has access to variables and methods listed in Pipeline Groovy Variables and Methods. You can find these variables methods using Variable Lookup help. The script must return true if the gate is applicable, or false otherwise. Â If no script is provided, the default is to return true (applicable). |
Continue | If checked, any failure will be ignored, and the pipeline execution will continue. |
Notify Pipeline Role | Selects one or more roles from the pipeline definition to notify in case of error. Default role members are defined on the pipeline, and optional overridden for each release. |
Test sets are defined to execute based on the testing strategy established on the project. Â Only those projects which are part of the release will have their test sets executed.
Script Variables
- style