Taurus Execution
Execution Settings
Execution objects represent actual underlying tool executions. You can launch unlimited number of JMeter’s, Gatling Tool’s, Grinder Tools, etc. Executions are configured under top-level config key execution. Specifying single execution config is equivalent to specifying array of executions with single element, for example:
--- execution: scenario: script: my-existing.jmx
is equivalent for
--- execution: - scenario: script: my-existing.jmx
However, users are encouraged to use array notation always to leverage the arrays auto-join capability when combining multiple config files into one. See config merge rules for more details on this.
There are load profile and scenario settings that are common for all execution types, and each executor type can also have its own settings.
Executor Types
Taurus tool may use different underlying tools as executors for scenarios. Currently supported tools are:
- JMeter, executor type jmeter
- Selenium, executor type selenium
- Gatling, executor type gatling
- Grinder, executor type grinder
- Locust, executor type locust
- PBench, executor type pbench
- Siege, executor type siege
- ApacheBenchmark, executor type ab
Default executor is jmeter and can be changed under general settings section.
--- settings: default-executor: jmeter
You may contribute your efforts in supporting requests-scenarios for your favorite tool by discussing this on project forum.
Load Profile
Execution has several options to set load profile settings. Support for options is specific to executor type. Available settings are:
- concurrency – number of target concurrent virtual users
- ramp-up – ramp-up time to reach target concurrency
- hold-for – time to hold target concurrency
- iterations – limit scenario iterations number
- throughput – apply RPS shaper, limiting maximum RPS to throughput
- steps – allows users to apply stepping ramp-up for concurrency and rps. Requires JMeter plugins to be installed!
--- execution: - concurrency: 10 ramp-up: 15s hold-for: 2m iterations: 1000 throughput: 20
Scenario
Scenario is a sequence of steps that is used to build script for underlying tool (e.g. generate JMX file for JMeter). Scenarios can be specified directly inside execution section. However, it is recommended to use special scenariostop-level config element to declare scenarios and access them through aliases. Some examples:
--- # embedded scenario execution: - scenario: requests: - http://localhost/1 - http://localhost/2
--- # referenced scenario scenarios: get-requests: requests: - http://localhost/1 - http://localhost/2 execution: - scenario: get-requests
Additional Files
When your execution requires additional files (e.g. JARs, certificates etc). you may use files option of execution and list paths for files there.
Note:- For Load testing purpose we will use jmeterÂ
Venkat Matta 