Resolution discrepancy

Hello everybody!
We’re a team that uses Robot Framework. The main dependency that we use is the FlaUI Library to test the application Avaloq Core Portal. Currently we’re using version 4.1.1 of the FlaUI Library.
To run our automated tests we have a Jenkins server that is connected to mutiple nodes.
When we run a test on a node the agent runs in an interactive console session.

We develop our tests locally on our private computers, that we connect to via RDP with the resolution 2560x1440. When we run these tests locally on our machines we seem to have no issues.
We’ve recently discovered that our agents are set to resolution 1920x1080 when we run through the interactive console session.

We’re currently assuming that our discrepancies in the test runs (works locally, fails in jenkins) could be caused by the different resolutions of our displays.

Now here we get to the actual issue: We currently cannot change the resolution of our machines because we connect to them via RDP, nor can we change the resolution of the agents.

Has anyone else run into this issue and can be of any assistance? If you need any additional information, let us know and we will provide that.

does the failure happen right away, eg even th efirst user interaction fails or app cannot be started or is it just at some random step in the test execution ?

reason for asking is that windows has “session 0 isolation”. This means: if jenkins slave is started via a service (typical if you dont know what you are doing) any code that gets executed in that node via jenkins cannot interact with the UI. Even if you open RDP session and you still have your RF called via pipeline directly into that “slave node”. So the real question is, what is the “communication channel” where you actually execute robot and its libraries from ?

When i was still managing bunch of jenkins for purpose of testing anything UI in windows:

  • jenkins slave has to be configured so that:
    • it automatically boots and logs in with predefined account - up until desktop is ready.
    • has SSH installed and running and appropriate ssh keys shared for authentication
    • has java installed.
  • then controller connects to the slave, copies the jar and starts the slave instance with the same account that already has the desktop open and logged in.

But please do share a bit more details about your pipeline

Hi Forbicina,

Welcome to the community,

When you make an RDP connection you should be able to set the screen size (It defaults to full screen) like this:

I would suggest trying this first and see if you can reproduce the issue and confirm this is actually the problem.

The questions I would ask next if I was in your position are:

  • can the resolution on the Jenkins runner’s be changed?
  • what screen resolution will the users in production have?
  • is screen scaling enabled on the Jenkins environment?
    • would screen scaling be enabled in prod?
    • do you need to test with screen scaling enabled
  • is the failure because the application window because the window is larger than the screen size?
  • are you running the application window maximised?
  • can you set the application window size (ensuring it’s less than 1920x1080)

Hopefully this helps you find the solution,

Dave.

FYI In my github runner’s on windows I run the following powershell command to set the screen resolution:

Set-DisplayResolution -Width 1920 -Height 1080 -Force

maybe you can do something similar in Jenkins with the resolution you want if that solves the issue

Dave.

For those interested: we solved the problem by using an HDMI dummy.
It simulates a connected display with a specific resolution.