npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

playwright-zephyr-junit-reporter

v1.0.0

Published

Playwright reporter that imports JUnit test results to Zephyr Squad (Zephyr for Jira Cloud) via the Test Automation API

Readme

playwright-zephyr-junit-reporter

A Playwright reporter that imports JUnit test results into Zephyr Squad for Jira Cloud via the Test Automation API.

Installation

npm install --save-dev playwright-zephyr-junit-reporter

Usage

Add both the built-in junit reporter and this reporter to your playwright.config.js. Both must point to the same output file — this reporter reads the file that junit writes.

// playwright.config.js
export default {
  reporter: [
    ['junit', { stripANSIControlSequences: true, outputFile: './playwright-report/junit/results.xml' }],
    ['playwright-zephyr-junit-reporter', {
      projectKey: process.env.ZEPHYR_PROJECT_KEY,
      accountId: process.env.ZEPHYR_ACCOUNT_ID,
      accessKey: process.env.ZEPHYR_ACCESS_KEY,
      secretKey: process.env.ZEPHYR_SECRET_KEY,
      jUnitFile: './playwright-report/junit/results.xml',
    }],
  ],
};

Configuration

| Option | Type | Required | Default | Description | |---|---|---|---|---| | projectKey | string | yes | — | Jira project key (e.g. PROJ) | | accountId | string | yes | — | Jira account ID of the user running the import | | accessKey | string | yes | — | Zephyr Squad access key | | secretKey | string | yes | — | Zephyr Squad secret key | | jUnitFile | string | yes | — | Path to the JUnit XML results file | | jobName | string | no | "Import tests results" | Display name for the automation job | | jobDescription | string | no | "Import automatic tests results from JUnit file." | Description for the automation job | | cycleName | string | no | "Playwright tests" | Test cycle name in Zephyr (current date/time is appended automatically) | | versionName | string | no | "Unscheduled" | Zephyr version/fix version name | | timeOut | number | no | 300000 | Upload job timeout in milliseconds |

Obtaining credentials

  • accessKey / secretKey: Generated in Jira under Apps → Zephyr Squad → API Keys.
  • accountId: Your Atlassian account ID, visible in your Jira profile URL or via the Jira REST API.

License

MIT