<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browsers on Selenium</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/categories/browsers/</link><description>Recent content in Browsers on Selenium</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 18 Sep 2025 10:46:23 +0200</lastBuildDate><atom:link href="https://deploy-preview-2575--selenium-dev.netlify.app/categories/browsers/index.xml" rel="self" type="application/rss+xml"/><item><title>A Curious Case of Selenium Manager Usage: What's Behind Chrome 127.0.6533.99?</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2025/selenium_manager_usage_whats_behind_chrome_127.0.6533.99/</link><pubDate>Sun, 14 Sep 2025 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2025/selenium_manager_usage_whats_behind_chrome_127.0.6533.99/</guid><description>&lt;p>Over the past two years, Selenium has included &lt;a href="https://www.selenium.dev/documentation/selenium_manager/">Selenium Manager&lt;/a>, a CLI tool (written in Rust) that provides &lt;strong>automatic management of drivers and browsers&lt;/strong> across all official language bindings (Java, JavaScript, Python, .NET, and Ruby). Its purpose is to simplify the developer experience: if you create a driver object like this:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-java" data-lang="java">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#000">WebDriver&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#000">driver&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#ce5c00;font-weight:bold">=&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#204a87;font-weight:bold">new&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline"> &lt;/span>&lt;span style="color:#000">ChromeDriver&lt;/span>&lt;span style="color:#000;font-weight:bold">();&lt;/span>&lt;span style="color:#f8f8f8;text-decoration:underline">
&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Selenium Manager takes care of detecting whether Chrome is installed, downloading the required driver, and even provisioning a copy of &lt;a href="https://googlechromelabs.github.io/chrome-for-testing/">Chrome for Testing (CfT)&lt;/a> if Chrome is not present on the system. This also works for Firefox and Edge, on Windows, Linux, and macOS.&lt;/p></description></item><item><title>Dev and Beta Channel Browsers via Docker Selenium</title><link>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2022/dev-and-beta-channel-browsers-via-docker-selenium/</link><pubDate>Tue, 23 Aug 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-2575--selenium-dev.netlify.app/blog/2022/dev-and-beta-channel-browsers-via-docker-selenium/</guid><description>&lt;p>The Docker Selenium browser Beta and Dev channel releases are now regularly published to &lt;a href="https://hub.docker.com/u/selenium">Docker Hub&lt;/a> and updated every two days. This enables testers and developers to test their applications on pre-release versions of Google Chrome, Mozilla Firefox, and Microsoft Edge before their official releases, using container tools, such as Docker. This empowers teams to stay ahead of the curve and catch potential showstoppers in their CI environment &lt;em>before&lt;/em> those issues have an impact on their users.&lt;/p></description></item></channel></rss>