@testream/playwright-reporter: Playwright test reporting for Jira

@testream/playwright-reporter publishes Playwright test results from CI/CD to Testream, where they become durable test evidence that teams can inspect from Jira. Playwright remains the execution source: Testream does not require you to recreate every automated test as a manual Jira case.

What the reporter sends to Testream and Jira

• Passed, failed, skipped, and flaky Playwright results
• Failure messages, stack traces, traces, screenshots, and videos
• Branch, commit, build, environment, and CI metadata, including merge-base data for pull-request comparisons
• Suite changes and historical trends for release and Jira visibility

For pull requests, the reporter uses an explicit TESTREAM_MERGE_BASE_SHA or provider-supplied merge-base metadata; otherwise it resolves git merge-base from the existing checkout without fetching. Keep history available (fetch-depth: 0 on GitHub Actions); if no merge base can be resolved, Testream falls back to execution-time comparison.

This gives engineering, QA, and product teams a shared view of current automated evidence without replacing the Playwright suite or CI pipeline they already use.

Install and configure

npm install --save-dev @testream/playwright-reporter

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

export default defineConfig({
  reporter: [
    ['@testream/playwright-reporter', {
      apiKey: process.env.TESTREAM_API_KEY,
      uploadEnabled: true,
    }],
  ],
});

Store TESTREAM_API_KEY as a protected CI secret. The reporter runs with Playwright and publishes structured evidence after the test run, so the same setup works in GitHub Actions, GitLab CI/CD, Azure Pipelines, Jenkins, and other command-based CI systems.

Playwright evidence in CI/CD

Keep running Playwright normally. Testream connects its results and artifacts to the relevant project, Jira work, and release context. Teams can inspect failures, compare suite changes, and follow quality trends while traces and browser evidence remain tied to the run that produced them.

Frequently asked questions

Do we need to recreate automated tests as manual Jira cases?

No. Your code-first Playwright suite remains the source of execution. Testream publishes its results as Jira-visible evidence without requiring a parallel manual test case for every automated test.

Does this work with Playwright projects and CI retries?

Yes. The reporter captures Playwright’s structured results across configured projects and preserves retry and failure context in the published run.

Official Testream resources

• Playwright Jira integration
• Complete Playwright reporter setup guide
• Install Testream – Automated Test Management for Jira