Integration¶
The stage allows to execute project-specific integration tests.
Typically, integration tests are very project-specific, thus they can be defined here using the stage extension mechanism.
Stage Content¶
This stage comprises following steps which are activated depending on your use-case/configuration:
step | step description |
---|---|
mavenExecuteIntegration | Runs backend integration tests via the Jacoco Maven-plugin |
npmExecuteScripts | Runs npm scripts to run generic integration tests written on JavaScript |
testsPublishResults | Publishes test results to Jenkins. It will automatically be active in cases tests are executed. |
Stage Activation¶
This stage will be active if any one of the following conditions is met:
- Stage configuration in config.yml file contains entries for this stage.
- Any of the conditions are met which are explained in the section Step Activation.
Step Activation¶
For this stage no conditions are assigned to steps.
Additional Stage Parameters¶
name | mandatory | default | possible values |
---|---|---|---|
script |
yes |
script
- The common script environment of the Jenkinsfile running. Typically the reference to the script calling the pipeline step is provided with thethis
parameter, as inscript: this
. This allows the function to access thecommonPipelineEnvironment
for retrieving, e.g. configuration parameters.
Configuration of Additional Stage Parameters¶
The stage parameters need to be defined in the section stages
of config.yml file.