@testream/webdriverio-reporter: WebdriverIO test reporting for Jira

@testream/webdriverio-reporter publishes WebdriverIO browser test results from CI/CD to Testream as durable evidence teams can inspect from Jira. It supports WDIO workflows built around Selenium or Cucumber while keeping the code-first test suite as the execution source.

What the reporter sends to Testream and Jira

• WebdriverIO suite and test outcomes
• Failure messages, stack traces, and bounded source evidence
• Branch, commit, build, environment, and CI metadata, including merge-base data for pull-request comparisons
• Suite changes and historical trends for Jira and release 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.

Testream adds a shared quality record without forcing teams to recreate every automated browser test as a manual Jira case.

Install and configure

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

// wdio.conf.ts
const testreamConfig = {
  apiKey: process.env.TESTREAM_API_KEY,
  uploadEnabled: true,
};

export const config = {
  reporters: [
    'spec',
    ['@testream/webdriverio-reporter', testreamConfig],
  ],
  services: [
    ['@testream/webdriverio-reporter', testreamConfig],
  ],
};

Generated CTRF reports are enriched with bounded source snippets when the report contains a test filePath and the source file can be matched by test name.

WebdriverIO evidence in CI/CD

Keep your existing WDIO command and store TESTREAM_API_KEY as a protected secret. The reporter publishes results from GitHub Actions, GitLab CI/CD, Azure Pipelines, Jenkins, or another command-based CI system, preserving browser-test and build context for later Jira review.

Frequently asked questions

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

No. WebdriverIO, Selenium, or Cucumber-compatible tests remain the execution source. Testream adds Jira reporting without a parallel manual case for each automated test.

Can it be used with Cucumber-style WDIO projects?

Yes. The reporter works with WebdriverIO result flows, including projects that use WDIO with Cucumber or Selenium-based browser automation.

Official Testream resources

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