Playwright GitHub Actions Reporting

What you’ll learn

How to stream Playwright test results from GitHub Actions to TestDino
How to group sharded matrix jobs into a single run

Set up a GitHub Actions workflow that streams Playwright test results to TestDino during the run and view aggregated analytics, failure analysis, and flaky test detection on your dashboard. This guide covers a basic workflow and a sharded workflow for parallel test execution across multiple shards.

Prerequisites

Before setting up, ensure you have:

A TestDino account with a project created
A TestDino API key (Generate API Keys)
A Playwright test project (or clone the TestDino Example Repository to get started)
@testdino/playwright installed and configured in playwright.config.ts|js|mjs:

npm install @testdino/playwright

playwright.config.ts

import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['@testdino/playwright', { token: process.env.TESTDINO_TOKEN, serverUrl: "https://reporter.testdino.com" }],
  ],
});

Keep any existing reporter entries, such as ['html']. TestDino runs alongside them and streams results as the run executes.

Store the API Key

Go to your GitHub repository
Open Settings → Secrets and variables → Actions
Click New repository secret
Name: TESTDINO_TOKEN
Value: Your TestDino API key
Click Add secret

Basic Workflow

Run your tests with TESTDINO_TOKEN set. Results stream to TestDino during the run, so no separate upload step is needed.

.github/workflows/test.yml — Basic workflow

.github/workflows/test.yml

name: Playwright Tests
on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Install dependencies
        run: npm ci

      - name: Install Playwright
        run: npx playwright install --with-deps

      - name: Run tests with TestDino
        env:
          TESTDINO_TOKEN: ${{ secrets.TESTDINO_TOKEN }}
          TESTDINO_SERVER_URL: https://reporter.testdino.com
        run: npx playwright test

Results stream live even when tests fail, so failures land on the dashboard without an if: always() step.

Sharded Tests

Run tests in parallel shards. Pass the same ciRunId to every shard so TestDino groups them into one run.

.github/workflows/test.yml — Sharded workflow

.github/workflows/test.yml

name: Playwright Tests
on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    strategy:
      fail-fast: false
      matrix:
        shardIndex: [1, 2, 3, 4]
        shardTotal: [4]
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Install dependencies
        run: npm ci

      - name: Install Playwright
        run: npx playwright install --with-deps

      - name: Run tests with TestDino
        env:
          TESTDINO_TOKEN: ${{ secrets.TESTDINO_TOKEN }}
          TESTDINO_SERVER_URL: https://reporter.testdino.com
        run: npx tdpw test --ci-run-id "${{ github.run_id }}-${{ github.run_attempt }}" -- --shard=${{ matrix.shardIndex }}/${{ matrix.shardTotal }}

Set the ciRunId reporter option in playwright.config to the same value if you prefer running npx playwright test directly instead of npx tdpw test.

Pipeline execution

After the workflow runs, GitHub Actions shows each matrix shard job in the workflow run view. Every shard streams its results, and TestDino merges them into one run. GitHub Actions workflow run showing 4 matrix shard jobs, each streaming Playwright results to TestDino

GitHub Actions workflow run showing 4 matrix shard jobs, each streaming Playwright results to TestDino

Results in TestDino

The test run appears in your TestDino dashboard with full failure details, flaky detection, and trend data as tests complete. TestDino Test Runs dashboard showing streamed results from GitHub Actions with pass/fail counts and AI Insights

TestDino Test Runs dashboard showing streamed results from GitHub Actions with pass/fail counts and AI Insights

Tag by Environment

Map branches to environments in project settings so runs route to the correct environment automatically. See Environment Mapping for the pattern rules.

Troubleshooting

Results not appearing on the dashboard

Confirm @testdino/playwright is in your playwright.config reporter array and TESTDINO_TOKEN is set in the run step. Results stream during the run, so no separate upload step is required.

Sharded runs show up as separate runs

Pass the same --ci-run-id (or ciRunId reporter option) to every shard. Different values create one run per shard.

TESTDINO_TOKEN not found

Confirm the secret is set in Settings → Secrets and variables → Actions. Secret names are case-sensitive.

Next Steps

CI Optimization

Reduce CI time with smart reruns

Branch Mapping

Map branches to environments for organized test runs

Integrations

Connect Slack, Jira, Linear, Asana, and more

GitHub App Integration

PR comments, CI checks, and pull request sync

Getting Started

Installation & Setup

AI & Automation

Debug & Analyze

Optimize CI

Test Management

Integrations

Administration

Prerequisites

Store the API Key

Basic Workflow

Sharded Tests

Pipeline execution

Results in TestDino

Tag by Environment

Troubleshooting

Next Steps

CI Optimization

Branch Mapping

Integrations

GitHub App Integration

​Prerequisites

​Store the API Key

​Basic Workflow

​Sharded Tests

​Pipeline execution

​Results in TestDino

​Tag by Environment

​Troubleshooting

​Next Steps

CI Optimization

Branch Mapping

Integrations

GitHub App Integration

Prerequisites

Store the API Key

Basic Workflow

Sharded Tests

Pipeline execution

Results in TestDino

Tag by Environment

Troubleshooting

Next Steps