jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Schumacher <felix.schumac...@internetallee.de>
Subject Re: SubResult Naming Policy
Date Sat, 21 Jul 2018 16:08:24 GMT


Am 17.07.2018 um 22:24 schrieb Philippe Mouawad:
> Hello,
> I attached a patch to:
>
> - https://bz.apache.org/bugzilla/show_bug.cgi?id=62550
Is subResultIndex incremented by one thread only?
Do you think anyone would like to have the old naming scheme configurable?

Regards,
  Felix

>
> Please review and comment.
>
> Test with embedded resource works.
> Regards
>
> On Tue, Jul 17, 2018 at 4:10 PM, Philippe Mouawad <
> p.mouawad@ubik-ingenierie.com> wrote:
>
>> Hello,
>> We would as a consequence to change property:
>>
>>
>>     - jmeter.save.saveservice.url=true
>>
>> Regards
>>
>> On Tue, Jul 17, 2018 at 7:29 AM, Philippe Mouawad <
>> p.mouawad@ubik-ingenierie.com> wrote:
>>
>>> Hello,
>>> With new version, subresults will also be available in CSV file.
>>> As a consequence they 'll be taken into account in dashboard:
>>>
>>>     - Hits Per Second which excluded embedded resources can now include
>>>     them
>>>
>>> But I think we need to make a modification on SubResults naming.
>>>
>>> Currently, they are named as per URL for HTTP Request for example.
>>> I suggest sub results follow naming policy so that they are correctly
>>> handled by Report.
>>>
>>> Thoughts ?
>>>
>>> Regards
>>> Philippe
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>> Ubik-Ingénierie
>>
>> UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/>
>>
>> UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>
>>
>>
>


Mime
View raw message