Hello,
I have been using Ranorex for almost 3 months now and have had great success in automating our software suite.
However, I have noticed some odd behavior on occasion.
I have created a test suite in Ranorex and have scheduled it to run once every day starting from a scheduled task. It is running on a system with a Ranorex runtime license. The majority of the time, it runs successfully, but sometimes it only runs part way through and then stops.
Upon reviewing the report, when it does not run successfully, I find the execution reports that it was aborted due to "The test run has been aborted by the user."
This occurs randomly. It might occur 5 minutes into the execution, or it might occur 30 minutes into the execution.
The system it is running on does not have a monitor, keyboard, or mouse attached to it, nor is it touched by anyone other than myself, so there is no way a user could have aborted it.
What could be causing this? There is no further details, or stacktrace as to what caused it, so I am unable to troubleshoot the root cause of this issue.
Thank you.
The test run has been aborted by the user
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: The test run has been aborted by the user
Hi,
Are you using multiple Threads, or are you manually abort such Threads in your Ranorex Solution?
Please try to comment the following line of code in your Programm.cs file out:
Regards,
Markus
Ranorex Support Team
Are you using multiple Threads, or are you manually abort such Threads in your Ranorex Solution?
Please try to comment the following line of code in your Programm.cs file out:
//Keyboard.AbortKey = System.Windows.Forms.Keys.Pause;Normally this error message is only shown if a thread was aborted.
Regards,
Markus
Ranorex Support Team
Re: The test run has been aborted by the user
I searched through the entire code, and confirmed that I am not using multiple threads, nor am I executing Thread.Abort on anything.
I am using Thread.Sleep in a couple of locations, to pause the current (and only) thread for a short period.
I commented out the Keyboard.AbortKey assignment in Program.cs.
This morning I re-ran the suite twice, and during one run, the "The test run has been aborted by the user" issue occurred again.
Is there any way to dig deeper into the root cause of this?
I am using Thread.Sleep in a couple of locations, to pause the current (and only) thread for a short period.
I commented out the Keyboard.AbortKey assignment in Program.cs.
This morning I re-ran the suite twice, and during one run, the "The test run has been aborted by the user" issue occurred again.
Is there any way to dig deeper into the root cause of this?
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: The test run has been aborted by the user
Hi,
Regards,
Peter
Ranorex Team
Would it be possible to send us your whole solution to [email protected] ? So we can check if there are any issues inside, because at the moment we have no clue why the test aborts. I would be also very helpful if you post us the settings for the scheduler.DMyers wrote:Is there any way to dig deeper into the root cause of this?
Regards,
Peter
Ranorex Team