It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×11,931
×10,908
×10
×10

question asked: May 04 '18, 5:08 p.m.
question was seen: 1,498 times
last updated: May 08 '18, 5:44 a.m.

Related questions

FAQ - How this Forum works

Can someone elaborate on the changes made in RQM 6.0.5 for Execution Variables?

0
Daniel Barbour (250●2●22) | asked May 04 '18, 5:08 p.m.

The New and Noteworthy section for RQM 6.0.5 states the following:


"Execution variables can now pass from result to keyword and from keyword to result

During the execution of a manual test script, execution variables are now passed from the previous step to a keyword step. Keywords can use those variables during execution and update their values. Keyword steps can also create new execution variables.

As soon as the keyword execution is finished, updated execution variables are available in the next step as well as in the test case result. Updates to the execution variable are available in the next step, whether it is a manual keyword step, an automated keyword step, or a manual step."

However - 6.0.4 already allowed the value of test script execution variables (type Artifact Variable) to be passed to keywords wherein, if modified (via a 'Set Execution Variable Step') the new value would be available in manual steps that follow the keyword steps.

Since the Help Information on Execution Variables for 6.0.5 does not appear to be noticeably different from that provided in 6.0.4 it is difficult for me to tell what changed for Execution Variables in an operational sense.
Can someone point me to any information that elaborates on this change (beyond what was provided in the 'New and Noteworthy' notes)?

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Subhajit Bhuiya (622●2) | answered May 07 '18, 3:08 p.m.
JAZZ DEVELOPER

The difference is "Keywords can use those variables during execution and update their values. Keyword steps can also create new execution variables."

Keyword step can set the variable and the updated value will be reflected in the next step. Basically now execution variable will be passed from parent script to keyword script and then keyword script to parent scrit again.

Comments
Daniel Barbour commented May 07 '18, 3:33 p.m.

Thank you - but, unfortunately, your answer does not address the fact that the behavior described for 6.0.5 doesn't seem any different that supported in version 6.0.4.  This is the basis for my question - how is it really different from the prior version(s)?.


Subhajit Bhuiya commented May 08 '18, 5:44 a.m.
JAZZ DEVELOPER

Try this in 6.0.4

Create a Set Execution Variable Step in the keyword script. Then Try to access that variable in the main script once the keyword execution is over.

Try the same thing in 6.0.5

Also try to use automated keyword and create or set execution variable in the automated script (Commandline Script). Once the keyword execution is over, try to access it from the main script.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.