How to Write End-to-End Tests for Chrome, Safari & Firefox Using Playwright

Getting started with everything you need to write end-to-end (E2E) tests using Microsoft’s Playwright browser automation & test library.

Marco Lüthy
9 min readSep 30, 2021
Macro photo of a lady bug
Bugs. They’re what we’re trying to avoid with our E2E tests. Photo by Timothy Dykes. Thank you, Timothy!

Playwright is an open source tool by Microsoft for browser automation and end-to-end testing. It’s like Google’s Puppeteer, or the archived Chromeless. Playwright can drive Chromium (Chrome), WebKit (Safari) and Firefox in both headed and headless modes (with and without windows on the screen.) It supports Typescript out of the box, too!

End-to-end (E2E) tests are not-really-unit tests in which real browsers are used to interact with a website or web app to check if things are working as expected. They’re commonly used to ensure that often-used UX/UI workflows like login pages or other app interactions are working correctly, often when it becomes too cumbersome to manually test everything in a SaaS product.

This article is Part 1 in a series of articles aimed at getting you started with everything you need to write end-to-end (E2E) tests using Playwright.

Articles in this series

  1. How to Write End-to-End Tests for Chrome, Safari & Firefox Using Playwright

--

--

Marco Lüthy

Hi there! I’m Marco. I write mostly about software development, sometimes about books I’ve read, and occasionally something else to keep things interesting.