jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Speteanu <asp.ad...@gmail.com>
Subject Re: jmeter.properties cleanup
Date Thu, 09 May 2013 10:38:48 GMT
I've used this one, since JMeter 2.3, I think:
onload.expandtree

and its one of the few things I configure when installing a new version.
People who create large trees in scripts know why its needed. But I'm
probably in the minority and know the GUI keyboard shortcuts to achieve the
same, so I wouldn't miss it.


On Wed, May 8, 2013 at 11:59 PM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:

> Hello,
>
> jmeter.properties has grown with a lot of properties that maybe are not
> that useful.
> I find it a good thing that lot of things are configurable in JMeter but
> maybe it's too much and one of the issues is users may not find the really
> useful ones (recently for example with https.socket.protocols).
>
> I propose to remove the following:
>
>    - jmeter.loggerpanel.display=false => It's so easy to just click it
>    - jmeter.errorscounter.display=true => Why would someone not want this
>    feature ?
>    - jmeter.toolbar.display=true => Why would someone not want this cool
>    feature ?
>    - jmeter.toolbar => Will users really want to reorganize these icons ?
>    - jmeter.toolbar.icons => Same as before
>    - onload.expandtree => Current default behaviour seems fine no ?
>    - jmeter.save.saveservice.autoflush => After some further thinking, why
>    would users not need this one ? If JMeter crashes and some data is lost
> ,
>    then there are big chances that the test was not that fine before the
> crash.
>
> I have doubts about those ones:
>
> # Netscape HTTP Cookie file
> cookies=cookies => What does it do ?
>
> We could try to remove them and if users want them, we would have some
> bugzilla request to get them back.
> --
> Regards
> Philippe
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message