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

protractor-errors

v2.0.0

Published

A protractor runner that allows you to run errors from previous runs.

Downloads

425

Readme

protractor-errors

A Jasmine wrapper for re-running failed Jasmine tests in Protractor.

install

npm install --save-dev protractor-errors or npm install -g protractor-errors to add cli

setup

required

Require the protractor-error module inside the Protractor config onPrepare function. This will execute the function that adds a JUnitXmlReporter to the Jasmine environment. If the params.errorsRun flag is set, the module will execute only errored specs from the most recent run inside the directory params.errorsPath. The error output is written to the directory params.errorsPath + params.currentTime.

var protractorErrors = require('protractor-errors');

// Below represents the protractor config file
exports.config = {
    // ...
    onPrepare: function() {
        protractorErrors.prepare();
    }
}

optional

Protractor errors now has the ability to filter out the successful suites. In order to use this please use the config function which will parse through the file globs in your original protractor config file, match the failed suites to the parent suite name and return back a list of just the failed files. This was ultimately created to reduce run time for error runs and to also reduce using unnecessary resources when pairing this with a cloud-based cross-browser testing tool.

var protractorErrors = require('protractor-errors');

// Pass the original protractor config into this config function
exports.config = protractorErrors.config({
    // ...
    onPrepare: function() {
        protractorErrors.prepare();
    }
})

If you want your errors run report to include the original run's results that did not change, call amend afterward.

var protractorErrors = require('protractor-errors');

// Below represents the protractor config file
exports.config = {
    // ...
    onComplete: function() {
        protractorErrors.amend();
    }
}

configuration

The module is configured by passing the following args or setting them inside the Protractor config:

params.errorsList: { suite: string; spec: string}[], params.errorsPath: string, directory where the JUnitXmlReporter will write output and the module will look for previous run data is no params.errorsList is defined. I recommend setting this in the Protractor configuration file since this should not change often.

params.currentTime: string, timestamp of the current test run. Triggering the test with the protractor-error cli runner will set this value automatically.

params.errorsRun?: boolean, default false, should the module limit the current run to previous errors

params.errorsTag?: string, mark the current run/reference previously tagged run for errors

Example:

protractor config.js --params.errorsPath 'jasmineReports' --params.currentTime '2017-01-24T23:53:06' --params.errorRun true

or

protractor-errors config.js --params.errorsPath 'jasmineReports' --params.errorRun true

cli

To automate setting the param.currentTime argument, trigger your protractor tests using the cli.

To run, either install protractor-errors globally and call: protractor-errors <config> [args] from the command line, with the same parameters you would call protractor. Or call the script by referencing the node_modules file directly: ./node_modules/protractor-errors/bin/protractor-errors.js <config> [args].