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

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.

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: ...

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

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

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.

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

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 }] ], });

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

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.

A complete step by step guide on how to setup Playwright in GitHub Actions with parallelization of both browsers and test cases.

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.

June 24, 2025 - GitHub Actions serves as a seamless solution, enabling developers to automate different facets of the software development lifecycle directly from their GitHub repository. ... Create a repository named “playwright_github_action”. Initially, ...

January 31, 2023 - # Run npm ci and get Playwright version - name: 🏗 Prepare Playwright env working-directory: ./path/to/tests run: | npm ci PLAYWRIGHT_VERSION=$(npm ls --json @playwright/test | jq --raw-output '.dependencies["@playwright/test"].version') echo "PLAYWRIGHT_VERSION=$PLAYWRIGHT_VERSION" >> $GITHUB_ENV # Cache browser binaries, cache key is based on Playwright version and OS - name: 🧰 Cache Playwright browser binaries uses: actions/cache@v3 id: playwright-cache with: path: "~/.cache/ms-playwright" key: "${{ runner.os }}-playwright-${{ env.PLAYWRIGHT_VERSION }}" restore-keys: | ${{ runner.os }}

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.

November 29, 2023 - My favourite is GitHub of course and as Playwright comes with a built in GitHub action all you need to do to have tests running on CI is simply push your code to a GitHub repo and watch the GitHub action do its job.

This step runs the Playwright tests. The --project flag specifies the browser to use for the tests, which is provided as an input when the workflow is manually triggered. ... - uses: actions/upload-artifact@v4 if: always() with: name: playwright-report path: playwright-report/ retention-days: 30