Convert Taurus yaml file as jmeter script

2,384 views
Skip to first unread message

Tong Sun

unread,
Mar 11, 2021, 10:44:12 AM3/11/21
to codename-taurus
Since the default-executor of Taurus is jmeter, there must be a way to convert Taurus yaml file as jmeter script. Is there any cli method to do that (without going through the GUI), just like the opposite of jmx2yaml?

thx

DT

unread,
Mar 11, 2021, 11:31:35 AM3/11/21
to codename-taurus

The contents of “Artifacts dir” are as follows:

 

  • bzt.log - the Taurus tool log. Contains the full output of the Taurus tool, very useful for troubleshooting
  • effective.json - the final Taurus configuration file in JSON format. It contains merged down input file(s), configuration defaults, any overridden properties, etc.
  • effective.yml - same as an effective.json but in YAML format. Taurus doesn’t differentiate between YAML and JSON and is able to consume any format so either option is fine.
  • errors.jtl - the JMeter result file in XML format with all diagnostic fields enabled. You will be able to see the full request and response details in View Results Tree listener.
  • example.yml - the YAML configuration file(s) provided via the command line to Taurus
  • jmeter-bzt.properties - any JMeter Properties overrides
  • jmeter.log - a very default JMeter log file
  • kpi.jtl  - the main results file, its name stands for Key Performance Indicators, it includes:
    • the sampler timestamp, label and duration
    • the response message and code
    • whether the sampler was successful or not
    • connect and latency metrics
    • active thread numbers
  • merged.json - a semi-final Taurus config file. It contains merged down, user-provided configuration files (YAML or JSON) but without defaults or overrides applied
  • merged.yml - same as above but in YAML format
  • modified_requests.jmx.jmx - same as requests.jmx plus Taurus-driven changes via YAML
  • requests.jmx - YAML configuration file converted to JMeter .jmx format
  • system.properties - effective JVM System Properties

So when you run your YAML file using JMeter executor the generated .jmx file is available under Artifacts Directory under the name of requests.jmx. Modifications introduced by Taurus are applied in modified_requests.jmx file and this guy is being opened in JMeter when you launch Taurus as bzt test.yaml -gui

Tong Sun

unread,
Mar 11, 2021, 11:53:34 AM3/11/21
to codename-taurus
Thanks a lot Dmitri for your detailed explanation!
Reply all
Reply to author
Forward
0 new messages