Issue with Maximizing Headless Chrome Browser on Jenkins while Using Cucumber and Watir

Other Questions Headless Browser
1

I’m experiencing a problem where my headless Chrome browser does not maximize during test execution on Jenkins, although it works perfectly on my local setup. Initially, I encountered this issue locally, but by implementing the following code, I was able to resolve it on my local machine: 

Before do |scenario|  DataMagic.load_for_scenario(scenario)  @browser = Watir::Browser.new :chrome, headless:true  screen_width = @browser.execute_script(‘return window.innerWidth;’)  screen_height = @browser.execute_script(‘return window.innerHeight;’)  @browser.driver.manage.window.resize_to(screen_width,screen_height)  @browser.driver.manage.window.move_to(0,0)end
However, it still fails on the Jenkins machine. I would appreciate any guidance on how to fix this issue. Thank you!

2

To handle the headless Chrome issue on Jenkins, try setting window size directly via Chrome options rather than relying on JavaScript. Update your code like this:

Before do |scenario|  
  DataMagic.load_for_scenario(scenario)  
  options = Selenium::WebDriver::Chrome::Options.new
  options.add_argument('--headless')
  options.add_argument('--window-size=1920,1080')
  @browser = Watir::Browser.new :chrome, options: options
end

This should ensure consistency in the browser's behavior across different environments.

3

When facing issues with headless Chrome in Jenkins, it’s important to ensure that the environment reflects your local setup as closely as possible. A potential difference could be the absence of a virtual display on Jenkins. You might want to consider using Xvfb (X Virtual Framebuffer) to mimic a display environment on Jenkins.

Here’s how you can configure it:

  1. Install Xvfb if it's not installed on your Jenkins machine. For most Linux systems, you can do this using sudo apt-get install xvfb.
  2. Wrap your test execution with Xvfb-run. For example, modify your Jenkins job to execute your tests as follows:
Xvfb-run --server-args="-screen 0, 1920x1080x24" cucumber

This approach will simulate a display environment, potentially resolving any quirks related to headless execution in Jenkins that differ from your local setup. It’s practical and does not interfere with your existing setup too much.