ITCAM for Tx: Robotic RFT script playbacks non simultaneous
ericmtn 1000009W88 Visits (7070)
This blog explains how Rational Functional Tester (RFT) test scripts are played back robotically with Rational Functional Tester installed on the Robotic Response Time agent.
RFT test scripts are played back robotically, one after the other, and not simultaneously on the Robotic Response Time agent.
Unlike Rational Performance Tester (RPT) HTTP scripts that are played back concurrently with the RPT runtime on the Robotic Response Time agent, RFT scripts are played back one after the other, sequentially, on the the Robotic Response Time agent.
There is no overlap of RFT script playback. Let's take the following example:
You have scheduled 2 RFT scripts to be played back on the the Robotic Response Time agent, using a robotic profile; and each application is setup with a 5 minutes playback frequency.
if the 1st script takes more than 5 minutes to complete, the 2nd script will not start when scheduled, but will wait until the 1st script will have finished. That's why you must configure your RFT scripts with caution, including verification points, and possibly extra coding in your script to make it error proof, so it handles unexpected scenario and unusual behavior of the application under test, like for example closing all the application left opened windows before actual start of script, etc..
One possible symptom that the scheduled script playback frequency is not reached is a message in TEP "Robotic Script Playback Status" view stating:
Current Run Status = "Overrun" or "Queued". example below:
For reference, every time a RFT script is played back robotically, the T6 robotic agent will start RFT, using java.exe command;
and a line like the following can be seen in ./BW
MIN - <RRT node name> - Play
Subscribe and follow us for all the latest information directly on your social feeds: