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

36 lines
1.0 KiB
Markdown
Raw Normal View History

2019-04-09 08:39:20 +02:00
# ${docGenStepName}
2019-04-09 08:39:20 +02:00
## ${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.
2019-04-09 08:39:20 +02:00
## ${docGenParameters}
2019-04-09 08:39:20 +02:00
## ${docGenConfiguration}
## ${docJenkinsPluginDependencies}
2019-05-24 15:41:49 +02:00
2019-04-09 08:39:20 +02:00
## Example
2019-04-09 08:39:20 +02:00
```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',
2019-04-09 08:39:20 +02:00
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.
2019-04-09 08:39:20 +02:00
`run docker run --rm -i --name \$CONTAINER_NAME --entrypoint /bin/bash \$IMAGE_NAME echo "Test"`