When installing Playwright using the VS Code extension or with npm init playwright@latest, you are given the option to add a GitHub Actions workflow. This creates a playwright.yml file inside a .github/workflows folder containing everything you need so that your tests run on each push and pull request into the main/master branch.

January 23, 2025 - This GitHub Action can be combined with the Upload Artifact action to upload test artifacts (like screenshots or logs). steps: - uses: microsoft/playwright-github-action@v1 - name: Install dependencies and run tests run: npm install && npm test - uses: actions/upload-artifact@v2 if: ${{ always() }} with: name: test-artifacts path: path/to/artifacts

September 19, 2024 - The first step was to figure out how to set up a Github Actions file that: ... name: Playwright Tests on: push: branches: [main, master] pull_request: branches: [main, master] jobs: playwright-tests: name: Playwright E2E Tests env: ...

This GitHub Action can be combined with the Upload Artifact action to upload test artifacts (like screenshots or logs). steps: - uses: microsoft/playwright-github-action@v1 - name: Install dependencies and run tests run: npm install && npm test - uses: actions/upload-artifact@v2 if: ${{ always() }} with: name: test-artifacts path: path/to/artifacts

March 25, 2025 - Open '.github/workflows/playwright.yml' and add the following workflow: on: [push, pull_request] jobs: test: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v3 - name: Set up Node.js uses: actions/setup-node@v3 with: node-version: 18 - name: Install dependencies run: npm ci - name: Install Playwright browsers run: npx playwright install --with-deps - name: Run Playwright tests run: npx playwright test

September 7, 2025 - Here’s the section from my GitHub Action that installs the browsers. It has never been a problem before, but I’ll explain how this is a little lazy and how I could streamline the installation to bring it under my 20-minute timeout. - name: Install Playwright Browsers run: npx playwright install --with-deps

November 13, 2023 - By using Playwright with GitHub Actions, you can automate your end-to-end tests to run on every push or on a specific time to ensure that your web application is always working as expected.

GitHub Actions support running jobs in a container by using the jobs.<job_id>.container option. This is useful to not pollute the host environment with dependencies and to have a consistent environment for e.g. screenshots/visual regression testing across different operating systems. ... name: Playwright Tests on: push: branches: [ main, master ] pull_request: branches: [ main, master ] jobs: playwright: name: 'Playwright Tests' runs-on: ubuntu-latest container: image: mcr.microsoft.com/playwright:v1.58.2-noble options: --user 1001 steps: - uses: actions/checkout@v5 - uses: actions/setup-node@v6 with: node-version: lts/* - name: Install dependencies run: npm ci - name: Run your tests run: npx playwright test

February 10, 2025 - Caches the node_modules and playwright binariesfolder to speed up dependencies installation using actions/cache@v4. Installs necessary Playwright browsers with npx playwright install --with-deps if the cache isn't hit. Executes Playwright tests using npx playwright test and extracts the number of failed tests from the Playwright report. Join Medium for free to get updates from this writer. ... Adds a comment to the pull request with the test results. ... Deploys the test report to GitHub Pages using actions/deploy-pages@v4 if there is any failure in test case execution

October 10, 2023 - What’s great about Github Actions worker integration is that a passing test, or failed one, also shows in your GitHub interface. For example, for every commit to Partytown we’ve been able to see if the code committed passed or failed. In our Partytown repo, we’re actually using two different jobs within the workflow. One is set up to run on a Mac with Safari, and the other is running on Ubuntu to test Chromium. Playwright certainly met our use cases for each of our projects, but it’s not the only great testing tool in town, and in fact, I encourage you to also do a good review of Cypress and choose what works best for your team.

Now that the playwright config is set up, you can run the tests with npx playwright test. At this point, we'll add a simple Github action workflow.yml file to run and upload the tests for pushes and pull requests.

GitHub action to setup Playwright in your CI workflows

import { defineConfig } from '@playwright/test'; import type { GitHubActionOptions } from '@estruyf/github-actions-reporter'; export default defineConfig({ reporter: [ ['@estruyf/github-actions-reporter', <GitHubActionOptions>{ title: 'My custom title', useDetails: true, showError: true }] ], });

This guide walks you through setting up GitHub Actions to execute Playwright tests for a Next.js 14 project.

To add a GitHub Actions file, first create .github/workflows folder and inside it add a playwright.yml file containing the example code below so that your tests run on each push and pull request for the main/master branch.

December 23, 2025 - Learn how to automate Playwright tests with GitHub Actions, optimize CI workflows, and ensure reliable, cross-browser testing for your application.

March 10, 2026 - The example workflow file below shows how to run Playwright tests in GitHub actions.

Playwright test report is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation. You can’t perform that action at this time.

September 5, 2022 - In this blog post I will show you how to setup a basic a Playwright project, integrate it into GitHub Actions and finally deploy an HTML report of the test results to GitHub Pages.