We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
The build agent was configured to be interactive.
I was able to resolve this by re-configuring the build agent and enabling autologon, this works now. :-)
I knew that this has got nothing to do with TestComplete in a way, but was hoping if someone would have come across same issue in Azure.
thanks
Hi,
> This operation requires an interactive window station.
In order for TestComplete/TestExecute to be able to interact with tested application's UI, your tested application must run in the non-locked active interactive user session (i.e. the user on behalf of whose account tests are executed must be interactively logged on into the system). This is essential requirement of the Windows OS, but not something specific for TestComplete.
So I think that you must provide interactive session on the remote machine first and then use it to execute automated tests.
I did not use Azure and Azure DevOps so, unfortunately, cannot help with exact steps but I hope that https://support.smartbear.com/testcomplete/docs/working-with/integration/azure/index.html help article will help you.
The build agent was configured to be interactive.
I was able to resolve this by re-configuring the build agent and enabling autologon, this works now. :-)
I knew that this has got nothing to do with TestComplete in a way, but was hoping if someone would have come across same issue in Azure.
thanks
Hi,
Yes, this seems to be the correct way.
Again, without too much knowledge about Azure DevOps but with the memories about Windows services:
-- Service, configured to be interactive is allowed to send messages to the user desktop if it is present. Service will do its job sulently/unattended if the desktop is absent;
-- Implemented autologon ensures that the user desktop is present and thus tested application can render its UI.