@pmaier1 cool with it?

Thinking out loud - I wonder what we should do about testing that the webUI "behaves nicely" when being displayed on a smaller device/window? It would be possible to run some CI with a smaller-sized browser window, but we can also just leave it to manual smoke-test to be done during release QA.

@phil-davis Do we have similar tests already, how much effort do you think is required for a full coverage?

@phil-davis Do we have similar tests already, how much effort do you think is required for a full coverage?

In web we set an env var, for example, "SCREEN_RESOLUTION": "375x812" to test with a mobile-phone-sized screen.

Here in the "traditional" oC10 UI we can do similar. Code like this resizes the window:
$this->getSession()->resizeWindow(375, 812, 'current');

We can add some code to do that if SCREEN_RESOLUTION is set. And then run whatever subset of test scenarios we like in CI with whatever SCREEN_RESOLUTION settings.

The "problem" is that we keep adding more CI pipelines! So maybe we just do it for a set of "smokeTest" scenarios.

I raised issue #38759 for that. Does not need to happen for this PR!

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
No Duplication information

@pmaier1 waiting for your go 👍

@pmaier1 waiting for your go

Fine for me 👍