It depends, somewhat, on what actually happens when you click on that link. What sort of window opens up, if any? When you say your computer gets locked, do you mean it goes to your own login screen/lock screen? Does it stop responding?
My guess... and this is just a guess... is that clicking on that link opens a modal dialog which needs to be closed before anything else can happen. The application does not return until the dialog is closed... if it doesn't return, TestComplete can't know what next to do.
This is considered an "Unexpected Window"... you may be able to handle it via the following instructions.
What happens when you try this test manually? Does it still lock up?
When I click on that link, I will be redirected to a new page in the same browser.
There are no models or whatsoever involved.
When I execute this test manually, that is what happens.
But when executed via Testcomplete it locks my computer as in I need to enter my windows password again, so that would be the lock screen indeed.
Because of this, testcomplete cannot continue with its test, unless I unlock the computer again.
This is only on the windows 10 pc where I logon via remote desktop btw.
Are you sure that you are not using key combination like WIN+L in your test?
Thank you for all the replies.
I am sure that I did not use a win+l key combination in my test.
The test had been running for a few seconds, maybe a minute and then it gets locked. So I cannot imagine that it would be the windows machine locking because of idlenes. Also because that feature should be disabled (but in Windows you never know ofcourse).
I was not trying to logon to remote desktop via testcomplete, I was already logged on via remote desktop and there the test was executed, which was just testing a webpage, nothing more.
The weird thing is: I have logged on via a different way and restarted the computer.. and now.. it seems to work normally again. As in, when I execute this test now, my computer is not getting locked. Therefore I think I might blame Windows.. but ofcourse, you can never be sure.
OK, so you login via remote desktop.... when your tests get to that point of your test case, how long have they been running and, when they are running, are they actually clicking via mouse, etc?
The reason being... it might not be the automation locking your machine but the Windows operating system doing so. If the machine is idle for a certain period of time, does it auto-lock? Is this something you can disable?
Are you trying to use TestComplete to log into the remote desktop?
