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)
Aborting test run too early can jam whole machine
- Support Team
- Site Admin
- Posts: 12167
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Graz, Austria
Re: Aborting test run too early can jam whole machine
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)
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)
Re: Aborting test run too early can jam whole machine
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.
"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.
Re: Aborting test run too early can jam whole machine
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:
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.
- Support Team
- Site Admin
- Posts: 12167
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Graz, Austria
Re: Aborting test run too early can jam whole machine
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)
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)