Page MenuHomePhabricator

Decide screen size for webdriver.io tests in CI
Open, Needs TriagePublic3 Estimated Story Points

Description

Today the tests in CI use the screen size: 1280x1024x24

https://gerrit.wikimedia.org/r/plugins/gitiles/integration/config/+/refs/heads/master/dockerfiles/node20-test-browser/run-with-xvfb.sh

That is a 5:4 aspect ratio. I think it makes sense to use 16:9 instead. What about using 1280×720 to have a more common aspect ratio and fever pixels to make the CI a little bit faster?

The bigger screen we use, ffmpeg will take more CPU power.

See also T408699

AC:

  • Document the new (or old) screen size we want to use and make a plan on how to implement it.

Event Timeline

Peter set the point value for this task to 3.Nov 4 2025, 5:52 AM
Peter edited projects, added: Test Platform (Taormina One 16); removed: Test Platform.

This is related to many different tasks about XVFB, video and screen sizes but I think what we can do now is to say that we should do a 16:9 screen size for desktop. I propose 1280×720 and then adjust our tests for that to work. If we switch to --headless instead of XVFB we could increase it.

Peter moved this task from In Progress to In Review on the Test Platform (Taormina One 16) board.

Assigning over for you for agreement in 16:9 and 1280×720. Let me know if you don't agree.

zeljkofilipin changed the task status from Open to In Progress.Nov 6 2025, 12:06 PM
zeljkofilipin triaged this task as Medium priority.
zeljkofilipin moved this task from Backlog 🪒 to Deep work 🌊 on the User-zeljkofilipin board.
zeljkofilipin changed the task status from In Progress to Open.Nov 20 2025, 11:46 AM
zeljkofilipin raised the priority of this task from Medium to Needs Triage.

I measured the difference. If we use ffmpeg and Xvfb a change to 1280×720 would make the tests ~6.8% faster and use something like 5.4% less CPU time. For headless there's a very little difference (below 1%).