In order to get a better picture of the results of our tests, we're trying to run them on a remote server.
Test Runner is configured to run on start-up - but it only seems to activate when a user remotes in to the headless server via RDP.
The machine is rebooted occasionally, and I typically discover this by selecting Run List Remotely in Test Studio - then finding no remote computers available to run my tests (these are tests of an ASP.NET MVC website).
When this happens, I remote into the server and Test Runner starts, then I can continue testing until the machine is rebooted again.
I tried creating a scheduled job via PowerShell to start the Test Runner via Telerik.TestStudio.Scheduling.Client.exe... but that doesn't seem to have solved the problem.
I found this in the Test Studio documentation: http://docs.telerik.com/teststudio/knowledge-base/scheduling-kb/keep-active-session
It says "Telerik tests running against HTML-based web applications (ASP .NET and others) frequently can work on a locked machine because most test steps don't use the mouse or keyboard."
That doesn't seem to be the issue - the issue here seems to be that a user account hasn't logged in in the first place.
The article also cautions against the approach documented on Windows Server 2008. The server I'm working with is Windows 2008 RT Enterprise SP1.
So what is the best way to correct this issue - preferably using PowerShell if scripting is required?
Test Runner is configured to run on start-up - but it only seems to activate when a user remotes in to the headless server via RDP.
The machine is rebooted occasionally, and I typically discover this by selecting Run List Remotely in Test Studio - then finding no remote computers available to run my tests (these are tests of an ASP.NET MVC website).
When this happens, I remote into the server and Test Runner starts, then I can continue testing until the machine is rebooted again.
I tried creating a scheduled job via PowerShell to start the Test Runner via Telerik.TestStudio.Scheduling.Client.exe... but that doesn't seem to have solved the problem.
I found this in the Test Studio documentation: http://docs.telerik.com/teststudio/knowledge-base/scheduling-kb/keep-active-session
It says "Telerik tests running against HTML-based web applications (ASP .NET and others) frequently can work on a locked machine because most test steps don't use the mouse or keyboard."
That doesn't seem to be the issue - the issue here seems to be that a user account hasn't logged in in the first place.
The article also cautions against the approach documented on Windows Server 2008. The server I'm working with is Windows 2008 RT Enterprise SP1.
So what is the best way to correct this issue - preferably using PowerShell if scripting is required?
3 Answers, 1 is accepted
0
Hi Mark,
The behavior you describe is the expected behavior. Our execution server, the process that actually runs the test, is an executable. This executable doesn't run until a user logs onto the machine. It just cannot run w/o someone being logged on in the first place. What you need is to configure the machine to automatically logon after boot up.
Regards,
Cody
Telerik
The behavior you describe is the expected behavior. Our execution server, the process that actually runs the test, is an executable. This executable doesn't run until a user logs onto the machine. It just cannot run w/o someone being logged on in the first place. What you need is to configure the machine to automatically logon after boot up.
Regards,
Cody
Telerik
0
Mark
Top achievements
Rank 1
Rank 1
answered on 19 Mar 2015, 06:31 PM
[quote]Cody said:
What you need is to configure the machine to automatically logon after boot up.
[/quote]
I set up an account with SysInternals AutoLogin for this purpose.
Next, I re-started the server. The server did not appear in the list of remote computers in the "Run Test List Remotely" window of Test Studio.
Two processes are running under the account - so it is logged in. Those services are:
Telerik.TestStudio.ExecutionManagerService.exe
CloudStorageSelfHost.exe
After logging in to the server myself, the server started to appear in the list of remote computers.
...so it seems that simply setting an account to auto-sign-in is not sufficient.
Any ideas as to what can be done to ensure that the auto-sign-in account allows the remote computer to appear in the "Run Test List Remotely" window?
What you need is to configure the machine to automatically logon after boot up.
[/quote]
I set up an account with SysInternals AutoLogin for this purpose.
Next, I re-started the server. The server did not appear in the list of remote computers in the "Run Test List Remotely" window of Test Studio.
Two processes are running under the account - so it is logged in. Those services are:
Telerik.TestStudio.ExecutionManagerService.exe
CloudStorageSelfHost.exe
After logging in to the server myself, the server started to appear in the list of remote computers.
...so it seems that simply setting an account to auto-sign-in is not sufficient.
Any ideas as to what can be done to ensure that the auto-sign-in account allows the remote computer to appear in the "Run Test List Remotely" window?
0
Hi Mark,
The two processes you listed are:
Regards,
Cody
Telerik
The two processes you listed are:
- Telerik Scheduling Service
- Telerik Storage Service
In that order. The process that's missing is Telerik.TestStudio.Scheduling.Client. This is the test runner. Make sure that"Run on startup" is checked as shown in the attached screen shot. Also make sure that the autologon is logging into the same account you used to check this checkbox. If you logged in as Joe and set this checkbox, but the autologon is for the account "Mary" the test runner will not automatically start up. It will only automatically start when "Joe" logs on either manually or automatically.
Regards,
Cody
Telerik