AbortKey has been pressed: but Ranorex hangs at Report.End()
Posted: Fri Jan 13, 2012 10:23 am
Hi all,
I wrote a simple test, best explained through the following pseudocode:
Dedicated to run over night, there are no problems. But when I arrive in the morning and use the Pause key to interrupt the running "test", then the message "AbortKey has been pressed" appears in the (command line window) log, but Ranorex (2.3.9) does not proceed (for hours). When I debug the running testcase, it is the line "Report.End();" ...
I need to go to the .../bin/Debug folder in order to get the *.rxlog.tmp file (gladfully just renaming it to *.rxlog works for me).
If I run the same for just some minutes, the Pause key works as expected.
Is this a problem of the large runtime? Any hints or ideas?
Through searching the forum, I found the registry key LowLevelHooksTimeout to be a possible cause. There is no Visual Studio installed, but the key did exist ...
I removed it, lets see if it helps.
regards, Björn
PS: a side note: "Pause" key works well to abort a running testcase, is there a key/function that just suspends the running testcase (like the "Break" Funktion in Ranorex)? UseCase: develop a 60 min long testcase, after 30 mins you figure out you forgot to implement one click. Currently you need to abort, code it, rerun the whole thing. With a "Break" key you can break, code it, do the click manually in the AUT, continue playback. Got used to it in IBM Rational Functional Tester (F12 there).
I wrote a simple test, best explained through the following pseudocode:
Code: Select all
while (true) {
start program;
load file;
close program;
}I need to go to the .../bin/Debug folder in order to get the *.rxlog.tmp file (gladfully just renaming it to *.rxlog works for me).
If I run the same for just some minutes, the Pause key works as expected.
Is this a problem of the large runtime? Any hints or ideas?
Through searching the forum, I found the registry key LowLevelHooksTimeout to be a possible cause. There is no Visual Studio installed, but the key did exist ...
I removed it, lets see if it helps.
regards, Björn
PS: a side note: "Pause" key works well to abort a running testcase, is there a key/function that just suspends the running testcase (like the "Break" Funktion in Ranorex)? UseCase: develop a 60 min long testcase, after 30 mins you figure out you forgot to implement one click. Currently you need to abort, code it, rerun the whole thing. With a "Break" key you can break, code it, do the click manually in the AUT, continue playback. Got used to it in IBM Rational Functional Tester (F12 there).