Installing TestGlance for Playwright

1. Make tests emit JUnit XML

Update playwright.config.ts (or playwright.config.js) so the JUnit reporter is enabled in CI. Playwright's JUnit reporter is built in — no extra package needed.

// playwright.config.ts
import { defineConfig } from '@playwright/test';
 
export default defineConfig({
  reporter: process.env.CI
    ? [['list'], ['junit', { outputFile: 'test-results/playwright.xml' }]]
    : [['list']],
});

2. Add the TestGlance step to CI

If the project already has a CI workflow that runs the tests, add this step to the test job (after the test step), and merge the permissions: block at the workflow's top level:

permissions:
  contents: read
  pull-requests: write
 
# ...inside the test job, after the test step:
- uses: testglance/action@v1
  if: always()
  with:
    github-token: ${{ github.token }}

If no CI workflow runs the tests yet, create .github/workflows/testglance.yml that runs the project's tests and then runs the TestGlance step.

if: always() matters — TestGlance should still run when tests fail. TestGlance auto-discovers anything matching **/test-results/*.xml, so no report-path is needed when reports land under test-results/.

3. Confirm with the user before committing

Summarize the diff and ask the user to confirm before staging or committing. Do not push.