Venkat Matta

it's all about the Performance Testing

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:

    script: my-existing.jmx

is equivalent for

- 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:

Default executor is jmeter and can be changed under general settings section.

  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!
- concurrency: 10
  ramp-up: 15s
  hold-for: 2m
  iterations: 1000
  throughput: 20


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
- scenario:
      - http://localhost/1
      - http://localhost/2
# referenced scenario
      - http://localhost/1
      - http://localhost/2

- 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 


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s


This entry was posted on March 22, 2016 by in Taurus.
%d bloggers like this: