jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Pokhilko <a...@ya.ru>
Subject Re: Having a globalVariables shared accross threads
Date Tue, 24 Oct 2017 08:27:12 GMT
Would not it be confusing? We have variables and properties which
already confuse users. Now we introduce something third. How would it
look from user's perspective?

Andrey Pokhilko

24.10.2017 11:09, Antonio Gomes Rodrigues пишет:
> +1
>
> Antonio
>
> 2017-10-24 9:55 GMT+02:00 Maxime Chassagneux <mchassagneux@apache.org>:
>
>> Hi Philippe,
>>
>> Nice idea, look good for me.
>>
>> +1.
>>
>>
>>
>> 2017-10-24 9:36 GMT+02:00 Philippe Mouawad <p.mouawad@ubik-ingenierie.com
>>> :
>>> Hello,
>>> There is frequently the need in Load Testing for sharing something
>> accross
>>> threads which might have been initialized in a setup Thread Group or by
>>> some Thread.
>>>
>>> Currently JMeter has 2 ways to do it:
>>>
>>>    - Properties but they are limited to String
>>>    - Through Beanshell (which is deprecated) through bsh.shared
>>>
>>>
>>> A recent illustration of this (but I frequently in my work need it) is
>> the
>>> Coverage Tests created for JMS, TCP and FTP.
>>> To do it I had to use Beanshell.
>>>
>>> So I propose to create such concept:
>>>
>>>    - JMeterContext would be enhanced with getSharedVariables()
>>>    - A new equivalent of JMeterVariables would be created. The Map would
>> be
>>>    ConcurrentHashMap
>>>    - It would be initialized/cleared in StandardJMeterEngine#run or
>>>    JMeterContextService.startTest();
>>>
>>> Thoughts ?
>>> --
>>> Regards.
>>> Philippe Mouawad.
>>> Ubik-Ingénierie
>>>


Mime
View raw message