Micro Focus QTP (UFT) Forums
how to force TEST to stop, rather than attempt to restart - Printable Version

+- Micro Focus QTP (UFT) Forums (https://www.learnqtp.com/forums)
+-- Forum: Micro Focus UFT (earlier known as QTP) (https://www.learnqtp.com/forums/Forum-Micro-Focus-UFT-earlier-known-as-QTP)
+--- Forum: UFT / QTP Beginners (https://www.learnqtp.com/forums/Forum-UFT-QTP-Beginners)
+--- Thread: how to force TEST to stop, rather than attempt to restart (/Thread-how-to-force-TEST-to-stop-rather-than-attempt-to-restart)



how to force TEST to stop, rather than attempt to restart - cocojava - 11-05-2010

QTP10
XP
IE8

This is my test, with no reuseable action. As you can see, it has two reuseable actions within it. Along with closing the browser when all inquires.

Code:
'RunAction "login", oneIteration
RunAction "flight inquires", allIterations
Browser("Flight Reservations").CloseAllTabs'

It runs through this process perfectly runing the first action of login and then to each flight inquiry, then closes the browsers.
To that point, the test results all check out.

BUT, This is what I don't want to happen...
Instead of the TEST ending and offering a 'passed' for results....
It then goes into the Action of 'login' and attempts to want to enter this again even when there isn't even a browser open.Sad


RE: how to force TEST to stop, rather than attempt to restart - sreekanth chilam - 11-06-2010

Go to QTP > File Menu > Settings > Run Tab > Choose "Run on Only One Iteration" radiobutton > Apply > OK.

Now re-execute your test & check .


RE: how to force TEST to stop, rather than attempt to restart - cocojava - 11-06-2010

This change did NOT change the previous run. Still has the same result.


RE: how to force TEST to stop, rather than attempt to restart - samchughtai - 06-03-2011

I have the same problem Im using QTP 9.5


RE: how to force TEST to stop, rather than attempt to restart - rajpes - 07-06-2011

Check your test flow in keyword view.
Sometimes when you create a new action and make it nested or try to change some properties, you may end up in having the same action call twice in the test flow.If it is duplicated this way, delete the unwanted action call