User Defined Variables

786 views
Skip to first unread message

beem...@gmail.com

unread,
Jul 29, 2015, 3:02:10 PM7/29/15
to codename-taurus
Hi Taurus Team,

I was wondering if it's currently possible to define user variables in yml?  This would be handy for me because I could easily create a sandbox, dev, sprint, ect variable file and simply include it as another parameter in the bzt command.

Thanks,
Mike

 

Andrey Pokhilko

unread,
Jul 29, 2015, 3:06:47 PM7/29/15
to codenam...@googlegroups.com
Yes, it is supported. See http://gettaurus.org/docs/JMeter/#modifications-for-existing-scripts , there is "variables" option on scenario level that will produce UDV for test plan, even existing.

Andrey Pohilko
Chief Scientist
P: +7 (909) 631-21-69
BlazeMeter
--
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/cb9f1b8c-87cd-4632-8d6a-902240429125%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

beem...@gmail.com

unread,
Jul 29, 2015, 3:24:55 PM7/29/15
to codename-taurus, and...@blazemeter.com
Hi Andrey,

Thanks for the quick response.  I see that you're able to define variables for existing jmx scripts but I haven't been able to get it working with scenarios.  What would I need to do in order to use the variables with an aliased scenario?

Lets say I have two files.

file one (main.yml):
---
execution
:
 iterations
: 1
 secenario
: test

 file two (test.yml)
---
scenarios
:
 test
:
   requests
:
   
-url http://test.com

I would like to be able to define variables for the test scenario in main.yml.

Thanks again,
Mike

Andrey Pokhilko

unread,
Jul 29, 2015, 3:28:22 PM7/29/15
to codenam...@googlegroups.com
---
scenarios
:
 test
:
   variables:
     varname: varvalue
     var2: val2
   requests:
   
-url http://test.com

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

Andrey Pokhilko

unread,
Jul 29, 2015, 3:29:27 PM7/29/15
to codenam...@googlegroups.com
And using it just like with jmeter,
---
scenarios
:
 test
:
   variables:
     var: someval
   requests:
   
-url http://test.com/${var}



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

beem...@gmail.com

unread,
Jul 29, 2015, 3:34:19 PM7/29/15
to codename-taurus, and...@blazemeter.com
Ok, thanks.  That will work for now.

yanilk...@gmail.com

unread,
Jun 11, 2018, 8:16:33 AM6/11/18
to codename-taurus
 Can we use this configuration on Locust executor too? How to parse the API response and store into the variables on Taurus LOCUST executor?  

Dmitri Pribysh

unread,
Jun 18, 2018, 7:22:15 AM6/18/18
to yanilk...@gmail.com, codename-taurus

Hi,

Currently, you have to write Locust script in Python yourself to perform this kind of actions.


  Dimitri
--
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.

yanilk...@gmail.com

unread,
Jun 30, 2018, 2:58:48 AM6/30/18
to codename-taurus
Thanks for the update. Do you have any plans to expand the Locust executor in Taurus?

Andrey Pokhilko

unread,
Jul 1, 2018, 7:35:29 AM7/1/18
to codenam...@googlegroups.com

Hi,

It's not in any close-term plans. If you are part of large organization that is customer of BlazeMeter, you can talk to BM reps to raise the priority, as for now we concentrate on JMeter and Selenium most.

--

Andrey Pokhilko
Open Source Initiatives Leader
CA
          BlazeMeter

30.06.2018 09:58, yanilk...@gmail.com пишет:
CAUTION: This email originated from outside of CA. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Reply all
Reply to author
Forward
0 new messages