The test run has been aborted by the user
Posted: Thu Aug 18, 2011 8:52 pm
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.
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.