Screen resolution of a VM using RDP with TestComplete
Hi, To test our desktop application we have a Master project that runs the Slave project on different VMs. We are using TeamCity to start our tests. On a TestManagement machine (VM)we have a Build Agent that is running as Service. This Build Agent starts the Master project with TestExecute. This project connects withRDP to different VM to run our UI Tests (Slave project)of our App.We are using Network Suite and run our tests on Hosts (VMs) like it is suggest here: Using Network Suite. But we have an issue with the screen resolution that is used to run our UI Tests. The resolution is too low. This page Running tests via RDP gives an explanation: "When running tests on a remote computer that participates in distributed testing, TestComplete creates a Remote Desktop session and automatically sets the master computer's screen resolution on the remote computer. This is done to avoid possible problems with test running." So TestExecute will use the master computer's screen resolution. But TeamCity Agent is run as a service on a VM (TestManagement machine) and there is no screen resolution because it's an headless machine and not like a real user that will connect with RDP to this VM and start the Master Project. I assume TestExecute will then use the default screen resolution (something like 640x480) as the resolution for the RDP connection. But this is too low to run our tests, some object are not on the screen and we have many issues... Is there a way to change the resolution used by the RDP connection that TestExecute / TestComplete will create ? The tricky part is that the Master project is started from a service on an headless machine... Thank you for your answers, Camille4KViews0likes9CommentsHas anyone had any joy creating and running tests on different size monitors
Hi all, My colleague and I are responsible for creating and running tests in TestComplete for our Desktop application. The problem we face is that we both have different size monitors/Laptops with different resolution etc. This means that tests created on one don't reliably work on the other. Has anybody else faced this issue and how did they solve it? Any ideas or suggestions would be greatly appreciated.Solved2.8KViews0likes17Comments