Skip to main content

Deep Dive into `headless=new` in Selenium

Image
By

Introduction

When it comes to automation testing, Selenium is a household name. With its extensive range of capabilities and flexibility, it has become an indispensable tool for quality assurance engineers. One of the most significant features of Selenium is its ability to run in headless mode, allowing testers to execute tests without the need for a visible browser instance. In this article, we'll delve into the world of headless mode, specifically exploring the `headless=new` parameter and its implications for Selenium testing.

What is Headless Mode?

Headless mode is a configuration option in Selenium that enables running browser instances without displaying a visible UI. This mode is particularly useful for automating tasks on cloud infrastructure, where a graphical interface is not available, or for running tests on a continuous integration/continuous deployment (CI/CD) pipeline. By default, when you use headless mode, Selenium will launch a browser instance in the background, allowing you to execute tests without visual rendering.

chrome headless=new
Chrome --headless old and new

Previously, headless mode was not just a mode but rather considered as another library. This meant that every feature had to be implemented separately for it, leading to a unique set of bugs not found in the Chrome library. Managing this not only demanded extensive effort from Chrome developers but also required users to handle a significant amount of customization for both headless and headed modes. As a result, the current setup illustrates that both headless and headfull modes utilize the same library, ensuring uniformity across functionalities. To delve deeper into the implementation details, you can refer to the blog post created by Chrome developers.

The `headless=new` Parameter

In recent Selenium versions, a new parameter called `headless=new` has been introduced. This parameter signals a significant shift in how headless mode operates. With `headless=new`, Selenium no longer treats headless mode as a separate entity from the standard, full-browser experience. Instead, it leverages the same codebase as the full-featured browser, ensuring that your tests are executed in a more authentic environment.

Why `headless=new` Matters

The introduction of `headless=new` addresses several limitations and drawbacks associated with traditional headless mode. I need to switch to the `--headless=new` because the old version is supporting the testing the Chrome extensions. I can create test cases and run it on headful mode but when I want to run it in headless mode in the CI, it starts failing. There many more benefits and some key benefits include:

  • Improved Compatibility: By sharing the same codebase as the full browser, `headless=new` ensures that your tests are executed in an environment that closely mirrors the real-world browsing experience.
  • Enhanced Stability: By leveraging the same rendering engine as the full browser, `headless=new` reduces the likelihood of issues and errors that were previously common in headless mode.
  • Simplified Maintenance: With `headless=new`, you can write tests that can be executed in both headless and full-browser modes, eliminating the need to maintain separate test suites.

Using headless=new in Selenium with Python

To take advantage of headless=new in Selenium with Python, follow these steps:

Install the required dependencies:

from selenium import webdriver
from selenium.webdriver.chrome.options import Options
from selenium.webdriver.chrome.service import Service
from webdriver_manager.chrome import ChromeDriverManager

Import the necessary modules:

options = Options()
options.add_argument("--headless=new")
options.add_argument("--disable-gpu")

    Configure the Chrome options:pip install selenium 

      service = Service(ChromeDriverManager().install())
      driver = webdriver.Chrome(service=service, options=options)

    Create a new instance of the Chrome driver pip install webdriver-manager

    from selenium import webdriver
    from selenium.webdriver.chrome.options import Options
    from selenium.webdriver.chrome.service import Service
    from webdriver_manager.chrome import ChromeDriverManager

    options = Options()
    options.add_argument("--headless=new")
    options.add_argument("--disable-gpu")

    service = Service(ChromeDriverManager().install())
    driver = webdriver.Chrome(service=service, options=options)

    driver.get("https://www.google.com")
    print(driver.title)
    driver.quit()

    Best Practices for headless=new

    When working with headless=new, keep the following best practices in mind:Use a recent version of Selenium: Ensure you're running the latest version of Selenium to take advantage of the headless=new features. Carefully consider your test environment: As headless=new uses the same codebase as the full Chrome browser, ensure your tests are designed to accommodate the increased resources required for headless mode. Monitor your system resources: Keep a close eye on system resources, such as memory and CPU usage, to avoid performance bottlenecks.

    Conclusion

    In conclusion, headless=new marks a significant improvement in Selenium's headless mode capabilities. By leveraging the same codebase as the full Chrome browser, you can now execute tests in a more authentic environment, enjoying improved compatibility, stability, and maintenance. By following the best practices outlined in this article, you'll be well on your way to unlocking the full potential of headless mode in Selenium with Python.

    avatar
    You

    Labels:Software testing

    Popular posts for software testing and automation

    Selenium Error "Element is not currently interactable and may not be manipulated"

    By
    Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last):   File "D:\workspace\sample_project\sample_run.py", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login     driver.find_element_by_id("id_username").clear()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r
    Read more

    Change Default Timeout and Wait Time of Capybara

    By
    One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg
    Read more

    Create an Alias for Interactive Console Work: Selenium and Capybara

    By
    If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each.  This post is for Windows machines, if you are using Unix-like see   this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby.  Create scripts in a directory called scripts (in your home folder, like as  ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py :  Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash
    Read more

    Page-Object Pattern for Selenium Test Automation with Python

    By
    Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part.   The last part is related to asserting your test cases against to the
    Read more

    Performance Testing on CI: Locust is running on Jenkins

    By
    For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients ,   hatch rate,  running locust without web interface and there should be so
    Read more