Bug 47302 - Ability to look at summaries without GUI (non-gui)
Summary: Ability to look at summaries without GUI (non-gui)
Status: RESOLVED DUPLICATE of bug 58653
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: unspecified
Hardware: PC Mac OS X 10.4
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2009-06-02 09:57 UTC by Martin Cleaver
Modified: 2015-12-29 22:31 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Martin Cleaver 2009-06-02 09:57:33 UTC
My issue is the same as the following email: I need to automate some 10+ tests on the same day, and just see how the responses vary day to day.

Having to open the desktop client is a complete non-starter for me.

I think there needs to be a way to extract the summary results.


On 09/04/2009, Woodcock, Simon <swood...@qualcomm.com> wrote:
> When in NON-GUI mode is there any way that you can save the results of a 
> 'Summary Report' to file in the same format as it appears in the table when 
> viewed in GUI mode, i.e. one entry per differently named request with an 
> average total for each request. As opposed to what I seem to get when I 
> currently write to file, which is a unique entry for every thread request.
>  I know I can 'Save Table Data' after the test has completed in GUI mode, 
> which gives me the desired format, however I want to run this in an automated 
> way in NON-GUI mode and then parse the results at a later date.
>  Your help would be much appreciated, thanks in advance,

Sorry, not possible; Listeners do not run in non-GUI mode.

However you can save the raw data and reload into a Summary Report
using the GUI.

Or just write your own analysis of the data.
Comment 1 Sebb 2009-06-02 11:28:53 UTC
If you don't want all of the Summary Results columns, you can use:


to write some info to the log file, and you can use grep or similar to extract it.
Comment 2 Martin Cleaver 2009-06-02 11:33:04 UTC
Thanks, Sebb.

I'd realised that.

The one piece of information I need in order to mass test meaningfully is the standard deviation for any given run.

Without this I can't tell whether something is awry on any given day.

I'm in #jmeter on irc://irc.Freenode.net if you would like to talk.

Comment 3 Sebb 2009-06-02 11:40:33 UTC
It's unlikely to be implemented in the near future, as it would mean changing the way that Listeners work.

If you use CSV output (which is more efficient), it should be fairly easy to use a stats package to extract exactly what you want, and more. Or use a scripting language such as Perl or Python, both of which have Maths libraries.
Comment 4 Martin Cleaver 2009-06-02 11:48:55 UTC
Yup, doubtless I can post process.

I noted that http://wiki.apache.org/jakarta-jmeter/LogAnalysis had a bunch of hacks for people wanting various data out of the system.

jmeter desktop gui with functionality to calculate these figures, so duplicating the functionality in perl and other scripting languages is only going to cause duplication and rework.

I realise that it is not on your roadmap and appreciate both the suggestion for workaround and listing as enhancement.

Comment 5 Martin Cleaver 2009-06-05 06:19:36 UTC
> jmeter desktop gui with functionality to calculate these figures, so duplicating the functionality in perl and other scripting languages is only going to cause duplication and rework.

I'm wondering: would it a lot of work to factor out the analysis code such that it can work on the raw data, and not hooked in via a listener?

It seems that anything that wraps around jmeter, e.g. http://wiki.apache.org/jakarta-jmeter/JMeterMavenPlugin or http://jchav.blogspot.com/ for regression testing, must be wanting this and other key outputs in its result set.

I am supposing that each is duplicating the work of the stddev numbers by test type. (Though I can't see the stddev output in the JChav, perhaps it was too much work, I've just asked on the blog.)

Comment 6 Andrey Pokhilko 2014-08-04 11:36:35 UTC
Since then, more tools have appeared, for instance http://jmeter-plugins.org/wiki/JMeterPluginsCMD/ , serving automation purposes.

This issue may be closed, I suppose. Solutions exist and listed.
Comment 7 Philippe Mouawad 2015-12-29 22:31:12 UTC
Since Bug 58653 and with Andrei answer I think we can close this one.

*** This bug has been marked as a duplicate of bug 58653 ***