1
0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-14 11:03:09 +02:00
sap-jenkins-library/documentation/docs/steps/batsExecuteTests.md
charly-lemee 0bba8f3d79
docs: fix typo in headline Prerequsites (#1461)
* fix: typo `Prerequsites`

* fix code climate finding

Co-authored-by: Christopher Fenner <26137398+CCFenner@users.noreply.github.com>
2020-04-26 19:50:39 +02:00

36 lines
1.0 KiB
Markdown

# ${docGenStepName}
## ${docGenDescription}
## Prerequisites
You need to have a Bats test file. By default you would put this into directory `src/test` within your source code repository.
## ${docGenParameters}
## ${docGenConfiguration}
## ${docJenkinsPluginDependencies}
## Example
```groovy
batsExecuteTests script:this
testsPublishResults junit: [pattern: '**/Test-*.xml', archive: true]
```
With `envVars` it is possible to pass either fixed values but also templates using [`commonPipelineEnvironment`](commonPipelineEnvironment.md).
Example:
```yaml
batsExecuteTests script: this, envVars = [
FIX_VALUE: 'my fixed value',
CONTAINER_NAME: '\${commonPipelineEnvironment.configuration.steps.executeBatsTests.dockerContainerName}',
IMAGE_NAME: '\${return commonPipelineEnvironment.getDockerImageNameAndTag()}'
]
```
This means within the test one could refer to environment variables by calling e.g.
`run docker run --rm -i --name \$CONTAINER_NAME --entrypoint /bin/bash \$IMAGE_NAME echo "Test"`