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

hermione-retry-command

v2.0.0

Published

Plugin to retry commands in hermione

Downloads

391

Readme

hermione-retry-command Build Status

Plugin for hermione to retry commands at low level.

You can read more about hermione plugins here.

Installation

npm install hermione-retry-command

Usage

Configuration

Plugin has the following configuration:

  • enabled (optional) Boolean – enable/disable the plugin; by default the plugin is enabled
  • rules (required) Array – describes set of conditions for which retries should run
    • condition (required) String
      • set blank-screenshot to retry screenshot commands that return blank screenshots
      • set assert-view-failed to retry assertView command if it has failed
    • browsers (optional) String|RegExp|Array<String|RegExp> – browsers in which retries should run, by default is /.*/ that means retries should run in all browsers
    • retryCount (optional) Integer – defines the number of retries. By default retryCount is set to 2
    • retryInterval (optional) Integer – defines delay in milliseconds before each retry. By default retryInterval is set to 100. Be careful when setting retry interval as this can dramatically downgrade performance of your tests.
    • retryOnlyFirst (optional, only for 'assert-view-failed') Boolean – defines the plugin operation limit for the first call command in the test. By default retryOnlyFirst is set to false.

Also you can override plugin parameters by CLI options or environment variables (see configparser). Use hermione_retry_command_ prefix for the environment variables and --hermione-retry-command- for the cli options.

Hermione usage

Add plugin to your hermione config file:

module.exports = {
    // ...
    plugins: {
        'hermione-retry-command': {
            enabled: true,
            rules: [
                {
                    condition: 'blank-screenshot',
                    browsers: ['MicrosoftEdge'],
                    retryCount: 5,
                    retryInterval: 120
                },
                {
                    condition: 'assert-view-failed',
                    browsers: ['Chrome'],
                    retryCount: 1,
                    retryOnlyFirst: true
                }
            ]
        }
    }
    //...
}

Testing

Run mocha tests:

npm run test-unit

Run eslint codestyle verification

npm run lint