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

@voicenter-team/cypress-reporter-pm2

v1.0.2

Published

Module that allows you to log cypress test results into pm2 metrics

Downloads

467

Readme

@voicenter-team/cypress-reporter-pm2

cypress-reporter-pm2 is a cypress plugin for creating metrics after cypress tests execution.

Install

# npm
npm install @voicenter-team/cypress-reporter-pm2 --save-dev

# yarn
yarn add @voicenter-team/cypress-reporter-pm2 --dev

Usage

Import cypress-reporter-pm2 into cypress/plugins/index.js

// cypress/plugins/index.js

require('dotenv').config()
const cypressReporterPm2 = require('@voicenter-team/cypress-reporter-pm2');

module.exports = (on, config) => {
    config.testFiles = [...JSON.parse(process.env.SPEC_TO_RUN)]
    cypressReporterPm2(on)

    return config
};

Create pm2 config file in the project root directory:

// test.config.js
require('dotenv').config()

module.exports = {
    apps: [{
        name: 'cypress-basic-test',
        script: './node_modules/@vue/cli-service/bin/vue-cli-service.js',
        watch: false,
        args: `test:e2e --url=${process.env.VUE_APP_URL} --headless`,
        cwd: './',
        restart_delay: 180000,
        env: {
            SPEC_TO_RUN: '["page.exist.spec.js", "check.name.spec.js"]'
        }
    }]
}

env.SPEC_TO_RUN should include stringified array of tests which should be executed.

Set VUE_APP_URL to .env or use hardcoded string instead.

Use restart_delay to set the interval time between tests execution (in milliseconds).

Execute:

pm2 start test.config.js

Parameters

  • on - cypress event emitter

  • namespace [string] - namespace for current application to differ it's metrics from other applications

  • options [object] - configuration for plugin.

    • namePrefix [string] - prefix for customizing metric key
    • nameSuffix [string] - suffix for customizing metric key
    • metricNameBuilder [function] - custom function for building metric key. @param {string} spec [spec name] @param {object} test [test data] @param {string} namespace [namespace] @return {string}
    • testNameParser [function] - custom function for parsing test name. @param {string} spec [spec name] @param {object} test [test data] @return {string}