Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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 TypeIdentifies 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 the expression drop-down.  The script must return true if the gate/step is applicable, or false otherwise.  If no script is provided, the default is to return true (applicable).

ContinueIf checked, any failure will be ignored, and the pipeline execution will continue.
Notify Pipeline RoleSelects 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.


  • No labels