Test Suite Monitoring for Playwright

Get Started in 3 Steps

1. 1Add the JUnit reporter to your playwright.config.ts — Playwright has it built in
2. 2Configure the reporter to write XML to a known path like `test-results/playwright.xml`
3. 3Add the TestGlance GitHub Action to your CI workflow

Reporter Configuration

// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({

  reporter: process.env.CI
    ? [['list'], ['junit', { outputFile: 'test-results/playwright.xml' }]]
    : [['list']],

});

GitHub Actions Workflow

# .github/workflows/test.yml
name: Tests
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm ci
      - run: npx playwright install --with-deps
      - name: Run tests
        run: npx playwright test
      - name: Report to TestGlance
        if: always()
        uses: testglance/action@v1
        with:
          api-key: ${{ secrets.TESTGLANCE_API_KEY }}
          report-path: test-results/playwright.xml

What You Get

• ✓Flaky test detection — automatically identify tests that pass and fail intermittently
• ✓Duration trends — track which tests are getting slower over time
• ✓Health score — a single metric summarizing your test suite reliability
• ✓CI summary — rich test result summaries directly in your GitHub Actions runs

FAQ