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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@gemini-testing/playwright-utils

v1.2.0

Published

Usefull playwright utilities

Downloads

12

Readme

playwright-utils

Usefull playwright utilities, such as fixtures, custom commands and matchers.

Installation

npm install --save-dev @gemini-testing/playwright-utils

Contents

Matchers

ToMatchScreenshot

looks-same based visual comparison. It uses CIEDE2000 based tolerance instead of pixelmatch (which is used under the hood of toHaveScreenshot) YIQ NTSC transmission color space threshold, which has severe problems calculating the color difference in shades of blue.

Usage

Setup:

// playwright.ts
import { test as base, expect } from "@playwright/test";
import { createMatchersFixture, type PlaywrightUtilsOptions } from "@gemini-testing/playwright-utils";

const test = base.extend<PlaywrightTestOptions & PlaywrightUtilsOptions>({
    ...createMatchersFixture(expect)
});

export { test, expect };
// playwright.config.ts
import { defineConfig, type PlaywrightTestOptions } from "@playwright/test";
import type { PlaywrightUtilsOptions } from "@gemini-testing/playwright-utils";

export default defineConfig<PlaywrightTestOptions, PlaywrightUtilsOptions>({
    // ...
    use: {
        // ...
        toMatchScreenshot: {
            // Default project config
            tolerance: 2.3,
            antialiasingTolerance: 4,
            maxDiffPixels: 0,
            maxDiffPixelRatio: 0,
            stopOnFirstImageDiff: false,
            saveImageOnScreenshotMatch: true,
            animations: "disabled",
            caret: "hide",
            maskColor: "#FF00FF",
            scale: "css",
            timeout: 30000,
            fullPage: false,
        }
    }
});

Usage:

await expect(page.locator("body")).toMatchScreenshot("plain", {
    // Comparison options, have higher priority than project options
    maxDiffPixels: 3
});

Args:

  • snapshotName: string
  • opts?: Object

Migration from toHaveScreenshot:

  • If you have toHaveScreenshot calls without specified name, it is required to name them.
  • Move contents of your toHaveScreenshot options from expect section of playwright config to toMatchScreenshot at use section of playwright config, then remove threshold property (toMatchScreenshot uses tolerance instead. Preferred value is 2.3).

Note: Screenshot comparison errors, caused by toMatchScreenshot, won't stop test execution by default. You can configure it with stopOnFirstImageDiff option.