How to set the correct timezone of Chrome in TestOps?

I tried both the Desired Capabilities and the ChromeDriver approach, but neither seems to have the desired effect. Locally my tests succeed (because it is run in the right timezone), but on TestOps they always fail. When I try to change the timezone in my Chrome sensors, I see the same behavior as in TestOps, so it should work by setting the timezone.

When trying to set the experimentalOption, I get this error message: “unrecognized chrome option: env” and when trying to set the timezoneOverride, I get this error message in TestOps: “No signature of method: org.openqa.selenium.remote.RemoteWebDriver$ByteBuddy$POaKSCv5.executeCdpCommand() is applicable for argument types: (String, HashMap) values: [Emulation.setTimezoneOverride, [timezoneId:Europe/Amsterdam]]

1 Like