Hello! I understand that during the playback (from RQM using the RFT adapter) the login window (toolbar pop-up) affects the playback scenario.

Yes, .activate() was one option - does not help, probably because the pop-up window is within the page

Have you checked on why the login is expected during the playback? perhaps the session expires mid-way? other reasons?

Can you please elaborate the failure case (with snapshots if possible) to help understand the scenario better?

Best Regards, Sunil

Thanks for your reply. Our RFT automated scripts are testing our client side application. Each script represents a work flow of a user through a particular module of the application.  The first step in all of our scripts is logging into the application.  This is handled through a call to an RFT script which executes the application and contains the steps for entering user name and password credentials.Execution of our RFT scripts directly from RFT, no matter what I have up on the screen currently, the script successfully calls the application and the log on screen shows up on the screen as the active window so that the script can enter the credentials.However, when I run our scripts using a test suite from RQM, if I have any window up on the screen, for example the RQM suite execution progress screen, instead of the log on window showing up on the screen active and ready for input it shows up on the tool bar as a flashing icon. I believe the application is going to the screen but not being pulled to the front.

This workaround does allow me to start the suite execution successfully.  However, the problem happens when an unexpected error is encountered during execution.  If anything interrupts the flow of the script, the script fails (which is expected).  But when the suite attempts to start the next test case in the flow the log on script cannot gain focus to enter the log on credentials and one after another all remaining test cases fail to execute.

So the question I have is, why is my log on window not being brought to the front and given focus when I execute from RQM, but it does when I run directly from RFT.  Secondly, if there was a way to explicitly force the window to the front within my RFT script that might alleviate the problem because then  behavior should not be dependent on the source of the script execution.

Thanks in advance.  We have been using RFT for quite a while but are new to trying to put our build runs under the umbrella of RQM.