Getting SendInput: Failed. Win32Error while running test list on remote VM

[Ankit]

Hi here,
Running the test list on Remote VMs & its failing, the message 'SendInput: Failed. Win32Error:' is shown as result !

Is there any way to fix the issue ?

[Tharinda]

check this out

http://docs.telerik.com/teststudio/knowledge-base/scheduling-kb/keep-active-session

[Ankit]

Hi tharinda
Thanks for reply,
but this already we are doing.

Some of the test (from test list) is passing, but some are failing with "Failed. Win32Error" message

[Tharinda]

Ok. But based on your error - "inputerror", i can only think of Telerik  not being able to send mouse and keyboard inputs to the pplication. check if your failing script contain mouse clicks and keyboard input simulations. Check if test runner is maximized to run the browser in full screen mode.

[Nikolay Petrov]

Hello Ankit,

To @Tharinda: thank you for pointing out the right direction here.

To keep an active session means not to minimize the active remote window as well. If that exception is the only one reason for tests failure to keep the active session would be the solution. 

Please have a look at this article if there are other problems when execution remotely as well.

Regards,
Nikolay Petrov
Telerik by Progress

 

[Elena]

Hi guys,

I wanted to post an update on this topic as there is a feasible solution implemented in Test Studio. 

So, this type of error is usually caused by the lack of active desktop session on the execution machine. This is a requirement for the UI functional tests executed in a head-ed mode of the browsers (not mandatory for headless Chrome execution).

You can read some additional details on this topic here and also check the solutions, which Test Studio suggests. The one I recommend is to take advantage of the built-in options to control the user session - ensure to enable the Keep Machine Awake and Reconnect to Console on Disconnect in the Test Runner on the remote machine and then close the RDP window. The session should be reconnected and the tests should be executed as expected. 

You could revisit your setups and try the suggested options from the Execution client.

Regards,
Elena
Progress Telerik