4.5Consuming Artifacts

In Pull Requests

Most CI platforms can parse JUnit XML and display test results directly in PRs:

• GitHub Actions: Use dorny/test-reporter action to add test results as PR checks
• GitLab CI: Use artifacts:reports:junit to show results in the merge request widget
• Jenkins: The JUnit plugin parses XML and shows results in the build page

# GitHub Actions: Show test results in PR
- uses: dorny/test-reporter@v1
  if: always()
  with:
    name: Playwright Tests
    path: results.xml
    reporter: java-junit

Downloading for Local Debugging

# GitHub CLI: Download artifacts from a specific run
gh run download 12345678 -n playwright-traces

# Open Playwright traces locally
npx playwright show-trace test-results/trace.zip

Aggregating Across Runs

For trend analysis, push test results to an external system:

• Allure TestOps: Aggregates results across runs and shows trends
• Grafana + InfluxDB: Custom dashboards for test metrics
• TestRail / Zephyr: Upload results via API for traceability