Sometimes when we execute a test in chrome headless it behaves differently than in our normal browser, this article will help you minimize the effect of using a headless browser and help you reduce flakiness when executing on headless.
Chrome Headless browser has different properties, for example:
Chrome uses —
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3205.0 Safari/537.36
Chrome Headless —
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/63.0.3205.0 Safari/537.36
There is also a difference in the request header Accept-Language:
Chrome uses —
Chrome Headless doesn’t set this header.
Make sure you are using the same resolution on Chrome Headless and normal chrome browser for your executions.
We can change these properties using the Selenium Desired Capabilities to start the driver with properties similar to normal Chrome:
"--user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.61 Safari/537.36",
You can set them on TestProject on the job like this:
Be sure to remove headless from the User-Agent, use this site to determine your user agent.
Request your application in the correct language in "lang=en"
Use excludeSwitches to remove the "Chrome is being controlled by automated test software" if needed.
Set resolution ("--window-size=1920,1080") or start maximized to set the same resolution you use on normal Chrome