InError set by the client. Client Error:
Failed to perform mouse action
BrowserCommand (Type:'Action',Info:'NotSet',Action:'RealMouseButtonAction',Target:'null',Data:'R,LeftDoubleClick,86,181,0',ClientId:'39628C5F69C491F695440F05AD2ECE5C',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Failed to perform mouse action')
InnerException: none.
InnerException:
ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
InError set by the client. Client Error:
Failed to perform mouse action
BrowserCommand (Type:'Action',Info:'NotSet',Action:'RealMouseButtonAction',Target:'null',Data:'R,LeftDoubleClick,86,181,0',ClientId:'39628C5F69C491F695440F05AD2ECE5C',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Failed to perform mouse action')
InnerException: none.
1 Answer, 1 is accepted
Hello Roland,
I reviewed the shared log and my suggestion will be to increase that execution delay you already added - the default timeout of 250 msec is really a short delay, so you can increase it to 1000 or 1500 msec. Then, check if the test run is consistent for all iterations.
Please, give this a try and let me know of the outcome.
Regards,
Elena
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
Rank 1
Hi Elena,
I tried gradually increasing it until I reached 10000 msec. Still getting the same outcome.
Thanks,
Roland
Hello Roland,
Thank you for your message. Elena is currently out of the office, so I will be stepping in on this ticket.
It is indeed quite unusual for one iteration to pass and another to fail, especially if the test list is executed under the same conditions. From what we can see, data-driven testing is being used with multiple user credentials. Could you please confirm whether all users in the data set are of the same type and have the same permissions?
In our experience, discrepancies like the one you're observing often occur when tests are executed with users who have different roles or access levels. This can result in variations in the UI or behavior of the application—such as landing on a different page—which may ultimately cause the test to fail.
To investigate further, we would need more information about the failure. Could you please share:
A screenshot or image of the application at the moment the failure occurs
Any error message that appears in the Step Failure Details or the execution log
As a final note, we have noticed that the application under test is publicly accessible. In such cases, we recommend opening a support ticket instead of posting in the public forum, so your data and testing assets remain confidential. In a support ticket, you can securely share the test file(s) and we’ll be able to take a closer look and provide more specific guidance on resolving the issue.
Looking forward to your confirmation and the requested details i a ticket.