Thank you Alex, this is a great detailed answer.
Nikolayev I checked your support case and see that the tests are running normally for you. Here's the article with requirements that need to be met:
Thanks for your suggestions, AlexKaras, Wamboo.
Shehnaz, do the suggestions help you resolve the issue?
Hi Shehnaz
I have the same Error message.
I didn't find answer on community so I recently open a case to the smartbear Support Team.
Our Jenkins Master is based on another server, that seems to be the only difference with you issue.
My Agent si installed as a service
His name is : jenkinsslave-G__jenkins_workspace
The windows service is set to run as "local service account" with "allow service to interact with desktop" checked.
I launch my tests and I have the Jenkins message ending with :
[TestComplete] Test runner exit code: -10 (Unable to create a user session).
... [TestComplete] Marking the build as FAILED.
Did you find a solution ?
Hi,
> service is set to run as "local service account" with "allow service to interact with desktop" checked.
To my knowledge, this setting allows service to display message boxes visible on the current desktop, but does not make service capable to create interactive user session.
The best solution (if not the only possible one) is to set Jenkins slave to run as an application within the user session. (Yes, you must ensure session's existence first.)
Hi Alex, Thank you for this.
" .... set Jenkins slave to run as an application within the user session".
I need to understand what you mean regarding what it is possible to do with Windows Server 2016.
Actually, the slave Jenkins node is set to use a Windows Service called "jenkinsslave-G__jenkins_workspace"
It don't works so you mean that I can try another way to call what "jenkinsslave-G__jenkins_workspace" do ?
You mean I have to create a application called "jenkinsslave-G__jenkins_workspace" with the JAR.
And then launch it on the server ?
how can I launch this if no user session is open ?
turn
Actually, the slave Jenkins node is set to use a Windows Service called "jenkinsslave-G__jenkins_workspace"
Hi,
> how can I launch this if no user session is open ?
Well...
-- In order for TestComplete (TestExecute, QTP, even Selenium) to be able to interact with the GUI of the tested application, this tested application must render its UI;
-- In order for the Windows application to be able to render its UI, it must have a desktop assigned to it;
-- In order for the application to have a desktop assigned to it, some user must be logged-in interactively and have active not locked user session.
So, if no user is logged-on interactively, there will be no active user session, there will be no desktop and the application started on behalf of this user (or any system account that does not have active user session with the desktop either) will not be able to render its UI. Thus test automation software will not be able to drive application's UI just because it is absent. Point.
For the GUI applications, slave Jenkins setup is usually like this:
-- slave box is configured to login automatically under some dedicated user;
-- This ensures active not locked user's session with desktop;
-- Scheduled task is set up to start Jenkins slave application on user logon;
-- This ensures that a) Jenkins master will be able to communicate with the slave; and b) that the application (TestComplete in our case) will be started by the slave within this user session;
-- Then TestComplete starts the tested application (again, within the user session that has desktop assigned), tested application obtains desktop where it can render its UI and thus TestComplete gets a possibility to drive the tested application via UI.
Impossibility to render UI if no desktop is assigned to user session is fundamental Windows OS behavior but not a limitation of TestComplete.
https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/preparing.html
might help.
