I'm not sure if this matters. I have noticed that when I've logged in as different users to run Test Studio during my testing of it I sometimes get an error message dialog which says "Error: Progress Telerik Test Studio Client application is already running!" which makes me think each time Test Studio starts it tries to start the local execution/scheduling server which seems like a bug since it was already started by another user. I'm using the local execution and scheduling server built into Test Studio. Should I install the standalone services even though everything will run on the same server? I'm not even sure if this scenario is supported and maybe I should just stick to a single user account that uses Test Studio.
Lastly, for the redirection to console functionality, I had a really tricky issue where some of my scheduled tests wouldn't run in the scenario where I closed my remote desktop connection. I used the video recording and notice that the page looked off and it was because the resolution of the console session was very low and that was somehow affecting mouse clicks (I believe) which ultimately led to the failure. I don't see that there is any way to set a resolution that the tests will run under, but if the execution server is running on the console I would think that it would have the ability to change the resolution at least for the duration of test execution. For now, I managed to change it using Dell's virtual console because I couldn't figure out a way to do it remotely using remote desktop.
3 Answers, 1 is accepted
Hello,
The execution server has the option to Run on start up, which you have enabled. With the current implementation we try to start it like an application with name Telerik.TestStudio.RemoteExecutorfor.exe for each user that logs in the machine. This is why you see the error message when you log in with another user. In case you encounter the same error in a different scenario, please share more details about the environment and steps to reproduce it on my end. I will then be able to analyze it and try to provide a solution or report a bug on your behalf.
You can execute test list locally or remotely, via the scheduling service and the execution server even if it is on the same machine with Test Studio. The remote execution requires you to have scheduling and storage servers and an execution server that is connected to those. You could use multiple different accounts to access Test Studio, as far as I know, and run your test lists locally or remotely, if you have configured scheduling and storage services and connected to them.
When you disconnect your RDP session, we use the TSCON Windows utility to connect your session to console. The problem appears to be that in that case the resolution of the console sessions falls back to the default resolution of the virtual machine which in your case appears to be too small. Since you mention that you have a working solution, I would suggest to keep using it until we manage to provide a built-in solution of the problem. You can follow the public bug report, which I created on your behalf.
I hope you will find the above information helpful. I remain available to continue our discussion.
Thank you for your valuable feedback. As a token of gratitude, I have updated your Telerik points balance.
Regards,
Plamen Mitrev
Progress Telerik
Rank 1
I'm having success after manually setting the resolution on the console. I haven't tried rebooting or anything yet, but I am assuming that the console resolution will persist. For others that may not have physical access to a console using the workaround of setting the resolution may not be possible.
The problem I see is that when I am physically at the server and need to connect a monitor to login on the console session there may be an issue if the monitor doesn't support the high resolution that my tests require, but that isn't a major concern for me at present.
Hello,
Thank you for sharing your solution to this issue here and in the public bug report. I hope that it is stable for you and can solve this issue until we include a fix in our future releases.
Regards,
Plamen Mitrev
Progress Telerik