It's all about the answers!

Ask a question

RQM - What is best practice for running the same test multiple times with different values?

Peter Hodges (3317) | asked May 23 '18, 11:23 a.m.

Hi all,

We've been using RQM more and more for automated testing (this specific test uses the Command Line Adapter). The test is passed variables in order to run. Originally, we wanted to somehow pass these values with Test Data, as we have used it for some manually testing in the past. We liked the way it behaved where you would run through the same steps in the Test Script for every row in the Test Data. Am I correct in saying that Test Data cannot be used with automated tests?

Our workaround for a while now has been to write the variables as Execution Variables on a Test Case. And then make a Test Case for every set of values we want to test and link to the same Test Script. This has been working really well but there's always been 5-6 permutations (or a dozen at most). Our more recent test has over 50 permutations and it doesn't seem like this method is the most appropriate way to handle this anymore. It certainly could, but I don't really want to direct others to make all those Test Cases if I don't have to.

The only reason we're not having a single test run through all the permutations itself is because we want that specific Pass/Fail information directly in RQM so we can report on it easily without having to dig through all the output files for the test. Is there a way to bubble up an automated test using the command line adapter into specific Test Steps in the same or similar way that other adapters/integrations work? That would work for us as well.

What do others do for this type of situation? What do you see that's currently working for you?


One answer

permanent link
Subhajit Bhuiya (6222) | answered May 31 '18, 6:24 a.m.

Till now commandline adapter does not have support for test data. One way can be create a automated keyword using the test script. Now insert that automated keyword multiple times into a manual test script. In between have set execution variable statement where you can change the values of the execution variable. When you will run the manual test script, 1st time automated script will be executed with default execution variable values. Then user will be prompted to assign new values to the execution variables which will be used by the next automated keyword step. The drawback with this approach is user needs to provide the values of the execution variable manually. To get rid off this limitation you ask open a RFE

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.