Taurus Task
Taurus is an automation-friendly framework for
continuous testing. Concord supports executing Taurus tests as a part of any
flow using taurus task.
Usage
To be able to use the task in a Concord flow, it must be added as a dependency:
configuration:
dependencies:
- mvn://com.walmartlabs.concord.plugins:taurus-task:1.32.3
Running Tests
The taurus task uses a number of input parameters
action: required, the name of the operation to perform;configs: required, list of configuration file(s) or configuration objects consumed by thetaurustool as input. More details in the configuration files section;ignoreErrors: boolean value, iftrueany errors that occur during the execution are ignored and stored in the result variable. Defaults tofalse;quiet: boolean value, iftrueonly errors and warnings printed to console. Defaults tofalse. Can not be used, ifverboseset totrue;verbose: boolean value, iftrueprints all logging messages to console. Defaults tofalse. Cannot be used ifquietset totrueproxy: string value, used for Taurus-based requests.downloadPlugins: boolean value, defaults tofalseand completely offline work. Iftruetries to download JMeter plugins at runtime.
The following example performs a run action with Taurus using the test.yml
configuration file:
flows:
default:
- task: taurus
in:
action: run
configs:
- test.yml
- log: "Taurus output: ${result.stdout}"
The execution status and logs are stored in the result variable.
Configuration Files
The plugins supports mixing and matching configuration files and inline configuration definitions:
configuration:
arguments:
someVar: "someValue"
flows:
default:
- task: taurus
in:
action: run
configs:
- a.yml
- b.yml
- scenarios:
myTest:
variables:
someVar: ${someVar} # example of using a flow variable
The inline configuration definitions will be saved as YAML files in a temporary directly. Taurus automatically merges all input configurations.
Expressions can be used in any input parameter including the inline configuration definitions.