jmeter.save.saveservice.output_format:xml seems to be ignored

[Eugen Jeno]

Hi,

I have the following yml file, taurus.additional.configs.yml:

#! /usr/local/bin/bzt

---

reporting:

  - module: junit-xml

    data-source: sample-labels

modules:

  blazemeter:

    disable: true

  jmeter:

    properties:

      jmeter.save.saveservice.output_format: xml

The command:

bzt -v resources/taurus.additional.configs.yml test.plans/dummy.jmx -o settings.artifacts-dir="results" -o modules.jmeter.path=/opt/jmeter/bin/jmeter

But the jmeter results are still in csv fomrat: kpi.jtl

How can I get them in xml format as with a normal jmeter run?

[Dmitri T]

It is by design, you cannot control the format of kpi.jtl file as postprocessing logic assumes that it doesn't change. It is possible to amend values in jmeter.properties and user.properties files and feed them to Taurus but certain properties will be ignored as Taurus explicitly relies on their default values.

Workaround: given you use your dummy.jmx file just add there Simple Data Writer listener, provide results file location, click "Configure", tick "Save As XML" box and select metrics you need to store. 

Be aware that XML output in general and storing response data in particular are resource consuming and can cause out of memory errors in case of large responses and severe load so use it wisely. 

[Andrey Pokhilko]

Hi,

kpi.jtl writer component has its own forced settings. There is plans to provide a flag to allow writing maximum verbosity trace XML, somewhere in the nearest future.

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/91027378-37f1-4bc7-ac70-9cb7bd345d36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.