You might experience unexpected outcomes while iterating a functional test script (RFT) triggered from RQM Web UI included to a Testcase/Testsuite.
Having a basic understanding of how datapool Iteration works locally from RFT and when integrated with RQM will help.
Let’s have a look at the options from RFT to manage datapool implementation.
RFT Iteration configuration setting:
1. RFT Eclipse has the option to set the iterations for a script while triggering the execution.
2. Programmatically iterating the data pool.
Option from RFT to set the Datapool Iteration when a script run is invoked
In the Datapool Iteration Count field, select a 'number' or 'Iterate Until Done' to specify how many times a test script runs when you run the script.
Option from RQM to set the Data pool Iteration when a script is created from RQM Web UI .
Construction>Create>Rational Functional Test Script >use test resources that are local to a test machine
Datapool iteration count: If there is a datapool associated with the script, you can pass the number of times the scripts must run by accessing the records from the datapool.
Here I have summarized the outcome based on the two approaches for driving a datapool from RFT script:
1.RFT Recorded script with associated datapool
2.RFT script written via descriptive programming approach
Next take a look at the way what the RQM triggered approach for the same script leads to :