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

@cuteribs/ado-playwright-reporter

v0.1.4

Published

Playwright custom reporter that pushes test results (with per-step outcomes) to Azure DevOps Test Cases already associated with an existing Test Run.

Readme

@cuteribs/ado-playwright-reporter

Playwright reporter that pushes test results - including per-test.step() outcomes - to Azure DevOps, into a Test Run that already exists (created by an Azure Pipelines "Run functional tests" / Test Plan build task, or manually). It never creates a run or test points itself; use @cuteribs/ado-testplan-cli to create/link the Test Suites and Test Cases ahead of time.

Install

npm install --save-dev @cuteribs/ado-playwright-reporter

Config

playwright.config.js:

export default defineConfig({
  reporter: [
    ['@cuteribs/ado-playwright-reporter', { config: 'ado.config.json' }],
    // or inline, skipping the config file:
    // ['@cuteribs/ado-playwright-reporter', { orgUrl: '...', project: '...' }],
  ],
});

ado.config.json only needs orgUrl and project for the reporter (no planId):

{ "orgUrl": "https://dev.azure.com/your-org", "project": "your-project" }

Environment variables:

  • AZURE_DEVOPS_PAT / SYSTEM_ACCESSTOKEN - PAT with Test Management (Read & Write).
  • TEST_RUNID - the existing ADO Test Run id. If unset, the reporter logs a warning and does nothing (safe no-op for local npx playwright test runs).

Matching results to ADO Test Cases

A Playwright test is matched to an ADO test result in the run by: automatedTestStorage = relative spec file path, automatedTestName = test title - the exact fields ado-testplan-cli writes onto each Test Case. If nothing matches, the test is logged as a warning and skipped (nothing is pushed for it).

What gets pushed per test

  • Overall outcome (Passed/Failed/Timeout/NotExecuted/Aborted), duration, error message.
  • Each test.step() as a subResult (outcome/duration/error), in source order - visible in ADO as the automated result's data-driven sub-results.

Notes

  • Retries: only the last attempt's result is kept (later onTestEnd calls for the same test overwrite earlier ones).
  • This package intentionally duplicates a small amount of config/client code from ado-testplan-cli instead of depending on a shared package, per project decision to publish exactly two independent packages.