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

mocha-proshot

v1.0.1

Published

Mocha reporter that takes screenshot after protractor tests

Downloads

12,240

Readme

mocha-proshot

A reporter for mocha that takes a screenshot after each failed Protractor test. The filename will be derived from the name of the failed test.

Installation

npm install --save-dev mocha-proshot

Usage

Use the environment variable PROSHOT_DIR to specify the base directory for all screenshots.

Simply update your Protractor configuration file to set the screenshot path and specify mocha-proshot as your reporter:

'use strict';

process.env.PROSHOT_DIR = './reports/screenshots';

exports.config = {
	...
    framework: 'mocha',
    mochaOpts: {
        reporter: 'mocha-proshot'
    },
	...
};

You probably want to use mocha-multi to get your usual test reports alongside the screenshots:

'use strict';

process.env.PROSHOT_DIR = './reports/screenshots';
process.env.multi = 'spec=- mocha-proshot=-'; // See 'mocha-multi' for configuration details

exports.config = {
	...
    framework: 'mocha',
    mochaOpts: {
        reporter: 'mocha-multi'
    },
	...
};

Caveat: mocha-multi does not work together with Protractor's sharding feature because the latter depends on some internals of builtin mocha reporters that mocha-multi does not emulate. Use mocha-proshot directly if you depend on sharding. See issue #1 for details.