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

@testiny/automation

v1.30.0

Published

A collection of utilities for importing automation reports into Testiny

Readme

Testiny Automation helpers

Use the Testiny automation helpers to import automated test case results into your Testiny Organization.

Playwright reporter

The Testiny Playwright reporter directly imports test results into Testiny while the test is running.

Add the Testiny reporter to your Playwright configuration like this:

const yourConfig = {
    ...
    reporter: [["@testiny/automation/reporters/playwright", {
        // enable or disable reporting to Testiny
        enable: true, 
        // defaults to Testiny Cloud App, set url for Testiny Server
        url: "",
        // optional: Testiny API key, defaults to environment variable TESTINY_API_KEY
        token: "tny_123...",
        // the name, key or id of the Testiny target project,
        project: "XYZ",
        // the name of the automation source to use - if the source does not exist it
        // will be created
        sourceName: "ui-test", 
        // optional: enables or disables attachment uploading, defaults to 'true'
        enableAttachments: true,
        // set to true to ignore errors and only log warnings instead, default to 'false'
        ignoreErrors: false,
        // completes automated test runs once the playwright run is complete
        // set to 'false' if multiple separate processes report into the same run(s)
        // and then use --complete-runs from '@testiny/cli' to close the run(s)
        completeRuns: true,
        // optional: your AUT version, will be added as aut_version
        autVersion: "1.2.3"
        // optional: the name of the CI environment, defaults to "auto"
        // will add multiple fields with the current CI context (e.g. build id, branch name, etc.)
        ciEnv: "gitlab",
        // optional: A list of field names to use for uniquely identifying test runs. 
        // Defaults to automatic detection from the CI environment
        runFields: ["ci_pipeline_id", "ci_job_id"],
        // optional: A pattern for creating test run titles out of field values, use %{field_name} as placeholders
        runTitlePattern: "Pipeline %{ci_pipeline_id} on branch %{vc_branch}"
        // optional: fixed field values which will be added to every test result
        fixedValues: {
            my_field: "test_456",
        },
        // optional: silent mode - do not log to stdout
        silent: false,
        // optional: specify list of annotation types to include on import
        customResultFields: ["type"],
        // optional: ID of a milestone to link newly created automation runs to
        milestoneId: "MS-123",
    }],
    ... more reporters
    ],
   ...
}