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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@aergonaut/playwright-opentelemetry-reporter

v0.2.0

Published

OpenTelemetry reporter for Playwright Test

Downloads

67

Readme

Playwright OpenTelemetry Reporter

Simple reporter that generates OpenTelemetry traces from Playwright test runs. You can then export these traces to your vendor of choice.

Example of trace in Honeycomb

Installation

Dependencies

Install the package with your favorite package manager:

$ npm install @aergonaut/playwright-opentelemetry-reporter --save-dev

You will also need to install the OpenTelemetry Node SDK and any other packages required by your vendor to export traces.

$ npm install @opentelemetry/sdk-trace-node --save-dev

Initialize the SDK

To collect traces, you must initialize the OpenTelemetry SDK before Playwright begins running your tests. The easiest way to do this is through globalSetup. For example:

// global-setup.ts
const sdk = new NodeSDK({
  traceExporter: new OTLPTraceExporter(),
  metricReader: new PeriodicExportingMetricReader({
    exporter: new ConsoleMetricExporter(),
  }),
});

export default async function globalSetup(_config: FullConfig) {
  sdk.start();

  return async () => {
    await sdk.shutdown();
  };
}

N.b. ensure your globalSetup functions returns a function that calls sdk.shutdown(). This will ensure that traces are exported before Playwright exits.

Configure Playwright

Configure Playwright to use your global-setup.ts and the reporter:

// playwright.config.ts
export default defineConfig({
  globalSetup: require.resolve("./global-setup.ts"),
  reporter: "@aergonaut/playwright-opentelemetry-reporter",
})

Usage

Generated Spans

This reporter generates spans for each test case and for each test step within each test case. Step spans are nested according to Playwright's internal organization. Practically, this means that work in before and after hooks will be grouped under nested spans, as will work to set up fixtures, etc.

Span Statuses

The reporter will set status on test spans and step spans according to the status of each test or step.

For step spans, if an error occurs during the step (e.g. a locator times out, or a click fails), the span's status will be set to ERROR and the error message will be recorded on the span.

For test spans, the span will only be set to ERROR if the test fails unexpectedly. Tests which are skipped or which pass will be UNSET. Similarly, expected errors (e.g. declared with test.fail) will also be UNSET.

Attaching Span Attributes

You can attach attributes to the test span by using Playwright test annotations. Your annotation type must start with the prefix pw_otel_reporter. in order to be attached to the span. Anything after the prefix will be used as the attribute name, and the description will be used as the attribute value.

To make constructing the type easier, you can use the annotationLabel function.

import { annotationLabel } from "@aergonaut/playwright-opentelemetry-reporter";

test("example test", async ({ page }) => {
  // ...
  test.info().annotations.push({
    type: annotationLabel("my_annotation"),
    description: "My custom annotation!",
  });
});

License

MIT.