Can I use global variable in [query] command?

Question

question

AdeelM asked Dec 18, '08 AdeelM posted Dec 18, '08

Can I use global variable in [query] command?

I have developed a response map for my response. I store the response in a variable using Store Response step property and make it a global variable. Say the variable name is "testcase_data".

How do I access this global variable in my query command. I have tried the following:

[query testcase_data (.//value)] --> This returns an error that variable cannot be found. This is understandable because accessing global variable requires the use of gget command.

[query [gget testcase_data] (.//value)] --> This returns an error "Invalid query".

[query \[gget testcase_data\] (.//value)] --> This returns an error "Unable to evaluate".

Any ideas?

-Adeel.

iTest response map

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2008-12-29T23:51:06Z

aswinbh answered Dec 29, '08 aswinbh posted Dec 29, '08

Thank you all for the response. We've a design issue here if I use the global variables. I have to use "call" to execute the test cases instead of "run" for my global variables to work. But, If I use "call", I won't get test reports per test case and "summarize" also has the same issue. I do need global variables to share data across all test cases and to create my own test reports using few counters(global variables). At the same time I do want individual test case reports generated by iTest. Please let us know how can I go about..

1

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KumarS commented · Dec 30, 2008 at 12:14 AM

Aswin

Variables do not make sense across multiple executions. For example, if you have these two executions performed by tcl (you can replace them with your favourite scripting language like perl):

tclsh a.tcl

tclsh b.tcl

The second tcl shell will have no idea about variables and their state in first tcl shell. You can think of "Run" action in iTest as similar. "Run" starts a new execution as if you manually started the execution from itestcli or iTest UI. That is why you get separate reports for "run" actions.

So only way for you to share data across different runs is to use "parameters" - but remember that "parameters" are readonly. You can set a whole bunch of parameters and then use "run" with testcase A and then run testcase B using the same or another set of parameters.

0 ·

Answer 2 · 2008-12-18T18:57:15Z

YujieL answered Dec 18, '08 YujieL posted Dec 18, '08

Have you tried using the Query dialog? Just put your the cell in edit mode, right click and you should see a Insert-->Query on Store response.

This dialog will help you insert a query with the correct syntax.

I've also attached an example that querys a stored response stored as global variable.

example.fftc (1.4 KiB)

puts__hello.ffrm (1.3 KiB)

5

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

aswinbh commented · Dec 22, 2008 at 09:15 PM

Hi,

Thanks for the response. But, I've another problem here.

I could get the query using "/data"only if we apply the response map in one of the steps of test case. If I apply the response map in a procedure, call the procedure in the test case and use query with "/data", it says "Invalid query".Please let me know if it's allowed or not.

Our basic requirement is, read the input file of the test-suite once and use the querries across the test cases. Please let me know if there's any other way of doing this.

0 ·

YujieL aswinbh commented · Dec 22, 2008 at 10:24 PM

I've attached an example where a test case can access the global variable created by another test case. In the child test case example.fftc, I added the procedure to the procedure library by going to the Procedure's General Properties and checking the checkbox "Include this procedure when listing callable procedures". Now I can call the child test case from the parent test case, and use the same query as before.

Message Edited by YujieL on 12-22-2008 02:25 PM

0 ·

parent.fftc (1.5 KiB)

puts__hello.ffrm (1.3 KiB)

example.fftc (1.3 KiB)

KumarS YujieL commented · Dec 23, 2008 at 12:24 AM

Thanks Yujie.

Ashwin - the important thing to remember is that "query" command works on a variable and a variable is defined by a location in an XML document in iTest. Variables inside procedures are only valid for the duration of the procedure call. So you will have to store the response and its mapping information in a global variable. Once you do that, you can use "query" command with "/data/your_global_var_name_here" to access all the queries produced by response mapping anywhere in your testcase.

0 ·

PaulD KumarS commented · Dec 23, 2008 at 02:11 AM

One extra hint: If you store responses in global variables, you just need to be careful that you don't put these in a huge loop, or something, with unique names for each variable. That's because this is like a "memory leak" -- in that you will be asking iTest to store more and more information in memory and eventually you could run out. This is no different than any programming situation. Just be careful about unlimited memory use -- especially for large responses.

0 ·

ramarb aswinbh commented · Dec 23, 2008 at 04:45 AM

If you would like to use one or two values in each test case from parent suite, then you may opt for passing arguments to procedures. In this case, no need to enable global variable option. I believe there will be no memory leak or performance issues in this case.

Do the following from your parent suite.

readfile c:\\test-suite.txt (provide response map and store response as 'response in step properties)

call :: project:///test_cases/new_testcase2.fftc?main -count [query response hello_pattern()] -value [query response col2(3)]

And, access them in your child script directly as $count or $value

0 ·

Answer 3 · 2008-12-18T18:56:42Z

KumarS answered Dec 18, '08 KumarS posted Dec 18, '08

Syntax for accessing global variables in a query is:

[query /data/testcase_data (.//value)]

I think we need to clean up the syntax so that user can simply pass in a flag instead of remembering "/data" syntax.

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

question