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-test-utils

v0.1.0

Published

Reusable Playwright test utilities: declarative network mocking, smart retry, accessibility assertions, and stable screenshot naming.

Readme

playwright-test-utils

Reusable Playwright test utilities — declarative network mocking, smart retry, accessibility assertions, and stable screenshot naming. Stop re-writing the same fixtures in every project.

CI npm version License: MIT Node

Every Playwright suite ends up re-implementing the same handful of helpers: intercepting network calls, retrying a flaky step, checking accessibility, and naming screenshots consistently. playwright-test-utils packages those into a small, well-tested, framework-idiomatic library so you can delete the boilerplate.

The matching/timing logic is pure and unit-tested; the browser-facing helpers are thin wrappers over Playwright's own APIs.

Features

  • mockNetwork — declarative, first-match-wins request mocking. Fulfill with JSON/body, set status, or abort to simulate failures.
  • retry — exponential-backoff retry for genuinely flaky steps, with an onRetry hook. Surfaces the final error instead of hiding it.
  • assertAccessible — one-line axe-core accessibility assertion with a readable, actionable failure message.
  • screenshotName — deterministic, filesystem-safe baseline names for visual diffs.
  • Tiny surface, typed throughout. Tree-shakeable named exports; @playwright/test stays a peer dependency.

Installation

npm install -D playwright-test-utils

@playwright/test is a peer dependency (you almost certainly already have it):

npm install -D @playwright/test

Requires Node.js >= 18.

Usage

Declarative network mocking

import { test, expect } from '@playwright/test';
import { mockNetwork } from 'playwright-test-utils';

test('renders users from the API', async ({ page }) => {
    await mockNetwork(page, [
        { url: 'https://api.example.com/users', json: [{ id: 1, name: 'Ada' }] },
        { url: 'https://api.example.com/*', status: 404 }, // catch-all fallback
        { url: /\/analytics\//, abort: true },             // block trackers
    ]);

    await page.goto('/');
    await expect(page.getByText('Ada')).toBeVisible();
});

Retry a flaky step

import { retry } from 'playwright-test-utils';

const token = await retry(() => fetchAuthToken(), {
    retries: 3,
    delayMs: 200,
    onRetry: (err, attempt) => console.warn(`auth retry #${attempt}:`, err),
});

Accessibility assertion

import { assertAccessible } from 'playwright-test-utils';

test('home page is accessible', async ({ page }) => {
    await page.goto('/');
    await assertAccessible(page, { disableRules: ['color-contrast'] });
});

Stable screenshot names

import { screenshotName } from 'playwright-test-utils';

test('home', async ({ page }, testInfo) => {
    await page.goto('/');
    await page.screenshot({
        path: `screenshots/${screenshotName({ project: testInfo.project.name, title: testInfo.title })}`,
    });
    // -> screenshots/chromium--home.png
});

Before / After

Before — copy-pasted into every spec:

await page.route('**/*', (route) => {
    const url = route.request().url();
    if (url.includes('/api/users')) {
        return route.fulfill({ status: 200, contentType: 'application/json', body: JSON.stringify(users) });
    }
    return route.continue();
});

After:

await mockNetwork(page, [{ url: '**/api/users', json: users }]);

Examples

Runnable Playwright specs live in examples/:

npm install
npx playwright install chromium
npm run example

Roadmap

  • [ ] v0.2mockNetwork request assertions (expect(mock).toHaveBeenRequested())
  • [ ] v0.3retry integration as a Playwright fixture (test.extend)
  • [ ] v0.4 — accessibility results as an attached HTML report artifact
  • [ ] v0.5 — test-data factory helpers
  • [ ] v1.0 — stable API + cookbook docs

Contributing

See CONTRIBUTING.md. The pure logic is covered by Vitest unit tests (npm test); browser behavior is demonstrated by the Playwright examples.

git clone https://github.com/fkhb90/playwright-test-utils.git
cd playwright-test-utils
npm install
npm test

Related projects

License

MIT © fkhb90