We want to run automated GUI tests on Windows Server 2008 64-bit SP2.
I connect to the Terminalserver with RDP from Windows Vista 32-bit. When GUI tests are running and I disconnect from the Terminalserver, then the tests fail because they run in a GUI-less mode after I disconnected. The problem and a solution is described on a web page. Unfortunately this forum prohibits me to add a link to this test ("Body text cannot contain images or links until we are able to verify your account.") Please google for: "Disconnecting From Remote Desktop Session While Running Automated Tests"
The solution is to use the "tscon" command. This works basically to solve the problem of the GUI-less Terminalserver after I disconnect.
But there is a problem with that solution in our environment. It does not seem to be common since I did not find any solution for the problem described below by googling.
After I disconnect with something like "tscon 2 /dest:console", the screen resolution on the Terminalserver changes to 640x480 pixels. Because of this our automated GUI tests fail since the application under tests needs a larger screen resolution. For instance a button cannot be clicked because a scroll would be required on such a small screen resolution. I know that the screen resolution changes to 640x480 pixel after using "tscon" because our automated tests make screenshots on an error.
When I reconnect to the Terminalserver, the screen size is as usual (1920x1080). But the windows on the desktop and the icons are compressed because the screen resolution has descreased after "tscon".
I tried a lot of things to solve this. I tried to use screen resolution parameters when connecting to the Terminalserver with RDP. I also looked into the registry on the Terminalserver for screen resolutions of 640x480 and increased them. Nothing worked.
Does anyone have an idea how to solve that problem with the screen resolution after using "tscon"?
I connect to the Terminalserver with RDP from Windows Vista 32-bit. When GUI tests are running and I disconnect from the Terminalserver, then the tests fail because they run in a GUI-less mode after I disconnected. The problem and a solution is described on a web page. Unfortunately this forum prohibits me to add a link to this test ("Body text cannot contain images or links until we are able to verify your account.") Please google for: "Disconnecting From Remote Desktop Session While Running Automated Tests"
The solution is to use the "tscon" command. This works basically to solve the problem of the GUI-less Terminalserver after I disconnect.
But there is a problem with that solution in our environment. It does not seem to be common since I did not find any solution for the problem described below by googling.
After I disconnect with something like "tscon 2 /dest:console", the screen resolution on the Terminalserver changes to 640x480 pixels. Because of this our automated GUI tests fail since the application under tests needs a larger screen resolution. For instance a button cannot be clicked because a scroll would be required on such a small screen resolution. I know that the screen resolution changes to 640x480 pixel after using "tscon" because our automated tests make screenshots on an error.
When I reconnect to the Terminalserver, the screen size is as usual (1920x1080). But the windows on the desktop and the icons are compressed because the screen resolution has descreased after "tscon".
I tried a lot of things to solve this. I tried to use screen resolution parameters when connecting to the Terminalserver with RDP. I also looked into the registry on the Terminalserver for screen resolutions of 640x480 and increased them. Nothing worked.
Does anyone have an idea how to solve that problem with the screen resolution after using "tscon"?