Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow setting the browser language

See original GitHub issue

Is your feature request related to a problem? Please describe.

Our application behaves differently according to the language of the browser. Currently, we have no way of influencing the language.

Describe the solution you’d like

Ideally, it would be possible to set environment variables when starting an element test in the cloud which are then consumed by the browser. Also effectively setting the browser language in elements would be a solution (either using the TestSettings or the browser interface).

Describe alternatives you’ve considered

Methods I tried:

setting parameters for chromium using --lang= doesn’t work due to restrictions of chromium itself
setting of environment variables is not supported when running in the cloud

Issue Analytics

State:
Created 3 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

sonnguyenmaucommented, Oct 12, 2020

Hi @torfmaster,

The --lang launchArg doesn’t work due to a bug of Puppeteer. However, as @honglax suggested, you can set the browser language by using extraHTTPHeaders in the TestSettings. In my case, this is what I used:

export const settings: TestSettings = {

	extraHTTPHeaders: { 'Accept-Language': 'bn' }
}

and this is the screenshot that I got when running the test on Flood (cloud), targeting Google. You can see that the language has been set to Bangla (Bangladesh)