---
title: "Improved Browser Testing on Heroku with Chrome"
description: "Automated browser tests on Heroku can fail when installed Chrome and Chromedriver versions drift apart, producing a mismatch error that stops the suite. The post introduces the community Chrome for Testing Heroku Buildpack, created to address installation reliability as Chrome continuously receives updates rather than pinning a browser version that quickly becomes outdated. Apps should remove existing Chrome and Chromedriver buildpacks and add heroku-community/chrome-for-testing as the first buildpack. By default it downloads Google's latest Stable release, while GOOGLE_CHROME_CHANNEL can select Stable, Beta, Dev, or Canary. After deployment, chrome and chromedriver are placed on the dyno PATH for tools including Selenium WebDriver and Puppeteer, providing executables for browser automation."
---

# Improved Browser Testing on Heroku with Chrome

[Heroku](https://yomu.fyi/company/heroku) · Mars Hall · Apr 9, 2024

**Type:** Announcement

## Summary

Automated browser tests on Heroku can fail when installed Chrome and Chromedriver versions drift apart, producing a mismatch error that stops the suite. The post introduces the community Chrome for Testing Heroku Buildpack, created to address installation reliability as Chrome continuously receives updates rather than pinning a browser version that quickly becomes outdated. Apps should remove existing Chrome and Chromedriver buildpacks and add heroku-community/chrome-for-testing as the first buildpack. By default it downloads Google's latest Stable release, while GOOGLE\_CHROME\_CHANNEL can select Stable, Beta, Dev, or Canary. After deployment, chrome and chromedriver are placed on the dyno PATH for tools including Selenium WebDriver and Puppeteer, providing executables for browser automation.

## Context

Heroku engineers found that automated Chrome tests were regularly disrupted by version mismatches between installed Chrome and Chromedriver components. Pinning a specific Chrome version is discouraged because Chrome continuously receives security updates and features.

## Approach / What changed

The Chrome for Testing Heroku Buildpack installs Chrome and Chromedriver together. Developers add heroku-community/chrome-for-testing as the app's first buildpack, optionally set GOOGLE\_CHROME\_CHANNEL to Stable, Beta, Dev, or Canary, and deploy the app.

## Takeaways

- The mismatch error occurs when Chromedriver supports one Chrome version while the installed browser is another.
- The buildpack defaults to Google's latest Stable release and supports Stable, Beta, Dev, and Canary channels through GOOGLE\_CHROME\_CHANNEL.
- After deployment, chrome and chromedriver executables are available on dyno PATH for browser automation tools such as Selenium WebDriver and Puppeteer.

**Tags:** [Heroku](https://yomu.fyi/topic/heroku)

- Source: [Heroku](https://www.heroku.com/blog/improved-browser-testing-on-heroku-with-chrome)
- Source URL: https://www.heroku.com/blog/improved-browser-testing-on-heroku-with-chrome
- Ingested by Yomu: 2026-09-09T20:05:00.918Z

[Read original post](https://www.heroku.com/blog/improved-browser-testing-on-heroku-with-chrome)