When building web applications, unit testing your individual components is certainly important. However, end-to-end testing provides assurance that the final user experience of your components chained together matches the expected behavior. Testing web application behavior locally in your browser can be helpful, but this approach isn’t efficient or reliable, especially as your application grows more complex.

Ideally, end-to-end tests in your browser are automated and integrated into your CI pipeline. Every time you commit a code change, your tests will run. Passing tests gives you the confidence that the application — as your end users experience it — behaves as expected.

For developers and businesses offering a web-based product, automated browser testing is a critical tool to ensure continuous delivery of a reliable service. Developers write browser tests by scripting actions against a real browser, simulating real usage by navigating, selecting, and making assertions about web pages and their document elements.

In this post, we introduce a new community buildpack that helps with automated browser testing. The new buildpack resolves installation reliability problems in the existing Chrome browser buildpacks for Heroku apps.

The need for speed takes on a new meaning in the face of a pandemic. With millions of lives at stake, everyone in the healthcare ecosystem, from medical facilities to laboratories to equipment manufacturers, races to do their part to help curb the spread.

With the coronavirus, the world put widespread diagnostic testing at the core of its pandemic response playbook. However, testing is only effective if the test results are accurate — a false negative could not only endanger the individual, but also their entire community.

Third-party quality assurance providers play a vital role in testing the tests. They make sure that test equipment and processes adhere to the highest standards. One...