Aborting test run too early can jam whole machine

Bug reports.
ArtoN
Posts: 4
Joined: Tue Oct 13, 2015 11:05 am

Aborting test run too early can jam whole machine

Post by ArtoN » Tue Dec 15, 2015 9:18 am

Preconditions:
- Keyboard and mouse has been disabled during test run
- AbortKey set

Steps:
- Start test run
- As soon as command prompt is opened for the execution of test executable, press abort key
=> Test run is stopped/paused but not fully aborted (testing neither proceeds nor ends)
=> Keyboard and mouse remains locked and only way to recover from that situation seem to be Ctrl+Alt+Del and then log off

Ranorex version: 5.4.3.26106
Windows version: Windows 7 Enterprise (SP1)

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Aborting test run too early can jam whole machine

Post by Support Team » Wed Dec 16, 2015 1:15 pm

Hi ArtoN,

Unfortunately I was not able to reproduce this issue on my machine.
May I ask you if you could provide a small sample Solution whereby this problem occurs?
Thank you.

Regards,
Markus (S)
.
Image

ArtoN
Posts: 4
Joined: Tue Oct 13, 2015 11:05 am

Re: Aborting test run too early can jam whole machine

Post by ArtoN » Wed Dec 16, 2015 2:43 pm

It should happen with all solutions as I reproduced it even with simple demo test project which were testing Windows Calculator. That project didn't have keyboard and mouse disabled so of course it didn't jam the computer but I could see that the command prompt stayed on screen just like with my official test project. The key thing to reproduce it is to abort test run as soon as the command prompt window (which executes the test executable) is shown. In Ranorex Studio side that means you are aborting the test run while modules are loaded. As result, Output window shows that some modules are loaded but then loading is aborted as output is something like this:
"Module Loaded: Ranorex.Core.Injector.dll
Module Loaded: Ranorex.Plugin.Mobile.dll
Module Loaded: "

...so looks like loading is interrupted as no file name is shown for last load.
But I'll disable the keyboard and mouse from that demo project and test if I can jam whole computer also with that project.

Martin
Posts: 152
Joined: Fri Aug 15, 2014 12:24 pm

Re: Aborting test run too early can jam whole machine

Post by Martin » Fri Dec 18, 2015 9:42 am

Code: Select all

Module Loaded: Ranorex.Plugin.Office.dll
Module Loaded: Ranorex.Plugin.RawText.dll
Module Loaded: Ranorex.Plugin.Java.dll
Module Loaded: Ranorex.Plugin.Sap.dll
Module Loaded: Ranorex.Plugin.Qt.dll
Module Loaded: Ranorex.Core.Injector.dll
Module Loaded: Ranorex.Plugin.Mobile.dll
Module Loaded: 
Module Loaded: Accessibility.dll
Module Loaded: System.Web.Services.dll
Module Loaded: 
Module Loaded: 
The last modules are loaded as empty for me as well on a successful run so I believe this is not the cause nor a consequence.

Nor can I reproduce the abort situation and freezing upon it. One solution would be to try and reinstall Ranorex together with .Net libraries and other prerequisites.

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Aborting test run too early can jam whole machine

Post by Support Team » Tue Dec 22, 2015 10:13 am

Hi ArtoN,

I could reproduce the problem when hitting the abort key in the exact moment you have described.
I'll forward this behavior to our corresponding department for further analysis.
Thank you.

Regards,
Markus (S)
.
Image