It's all about the answers!

Ask a question

Best Practices for using Execution Variables?

Dana Watts (141617) | asked May 05 '14, 7:31 p.m.
edited May 07 '14, 9:45 a.m. by Max Bridges (24126)
I'd like some guidance on how best to utilize the execution variable functionality within RQM.  We have a number of test suites which utilize multiple test cases/scripts.  There are often situations where the same test case/script is utilized multiple times within a test suite but will need different data (ie Add New Person could be called multiple times when adding multiple people to a form). 

In this sort of situation, how would I utilize the execution variables to allow us to reuse the same script multiple times?

In Quality Center, this can done by creating a "script library" (for lack of better term) where each potential variable step is given a parameter inside the script.  Then when writing the scenario, we "call" the test script and are prompted to enter the data value for the parameter within the script.  This is done for each unique call to the script allowing for modular and reusable scripting.  Is there a similar functionality in RQM?

Example Test Suite:
1. Add New Person (first name: John, last name: Smith)
2. Run Credit Scoring
3. Add New Person (first name: Debbie, last name: Smith)
4. Run Credit Scoring
5. Create Form

One answer

permanent link
Don Yang (7.7k21110138) | answered May 06 '14, 3:47 a.m.
Please see "Create Set Execution Variable Step" in
would do the job for you. It allows the script to prompt the user to input the value during execution of a script.

Dana Watts commented May 06 '14, 1:07 p.m.

Thanks Don but in having the prompt for the data come during execution, we're still required to maintain some sort of documentation outside of Rational which includes the data values that the tester should use.

We're trying to avoid this if at all possible b/c our client is not inclined to have to have rational open, an excel spreadsheet with data values, and the application open during testing.

Is there no way to add the data values to the test suite as part of the planning process so that when when we execute the script, it pre-populates the variables with the values?

Don Yang commented May 06 '14, 10:44 p.m.

your test scenario seems to me is more suitable in using test data(datapool concept) instead of execution variables. Please see the details in :

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.