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

easy-click

v1.1.2

Published

## Installation * NodeJS could be download at: [link](https://nodejs.org/)

Downloads

3

Readme

easy-click

Installation

  • NodeJS could be download at: link

Run Auto Tests:

npm run test

Generate Html Report

npm run report

Docs:

Browser Steps

Given

  • Given opened page path '<url-path>'
  • Given opened page url '<url>'
  • Given mock the requests to an '(.*)' url with '(.*)' data
  • Given mock the requests to an '(.*)' url regexp with '(.*)' data

When

  • When I press (back|forward|refresh)
  • When I scroll (up|down)
  • When I set browser view port: '(\d*)' width, '(\d*)' height
  • When I set key='<local-storage-key>', value='<local-storage-value>' in local storage
  • When I (select|close) (\d*) page
  • When I (set|clear) cache

Then

  • Then I expect the browser url (matches|equal|contains|start with|end with) '<value>'
  • Then I expect the page title (matches|equal|equal ignore case|equal ignore spaces|contains|contain ignore case|contain ignore spaces|start with|end with) '<title>'
  • Then I expect the page source is amp
  • Then I expect the (viewport|full) page is the same look as '<expected-image-name>' image
  • Then I expect the (viewport|full) page has look as '<expected-image-name>' image with inconsistency of (\d*) percentage

Cookie Steps

When

  • When I clear cookies
  • When I delete '<cookie-name>' cookie
  • When I set cookie: '<cookie-name>' name, 'cookie-value' value
  • When I set '<cookie-name>' cookie into local storage '<local-storage-key>'

Then

  • Then I expect the cookie '<cookie-name>' name has( not)? '<expected-cookie-value>' value
  • Then I expect the cookie '<cookie-name>' name( not)? exist

WebElement Steps

When

  • When I click on '<xpath|css>' element
  • When I click on '<xpath|css>' element and wait (\d*) seconds
  • When I click on '<xpath|css>' element with (\d*) index
  • When I click on '<xpath|css>' element with '<text>' text
  • When I click on the '<text>' text
  • When I click on '<text>' text with (\d*) index
  • When I click on '<xpath|css>' element and wait for navigation
  • When I wait and click on '<xpath|css>' element
  • When I type '<value>' value into '<xpath|css>' element
  • When I type '<value>' value into '<xpath|css>' element with delay (\d*) ms for each key press
  • When I press the '<key>' key
  • When I press the '<key>' key a (\d*) times
  • When I press the '<key>' key on the '<xpath|css>' element
  • When I (blur on|focus on|hover over) '<xpath|css>' element
  • When I upload '<file-path>' file via '<xpath|css>' element
  • When I select '<value>' value in '<xpath|css>' select
  • When I clear value in '<xpath|css>' element
  • When I set '<attr-name>' attribute '<attr-value>' value into '<xpath|css>' element
  • When I (add|remove) '<class-value>' class of '<xpath|css>' element
  • When I set '<value>' value into '<xpath|css>' element
  • When I set '<xpath|css>' element (value|text) into '<local-storage-key>' local storage
  • When I set '<xpath|css>' element attribute '<attribute-name>' value into '<local-storage-key>' local storage
  • When I set '<xpath|css>' element selected option into '<local-storage-key>' local storage
  • When I set '<xpath|css>' element options into '<local-storage-key>' local storage
  • When I trigger '<event-name>' event into '<xpath|css>' element
  • When I scroll to '<css>' element
  • When I scroll to '<css>' element and wait (\d*) seconds

Then

  • Then I expect the '<css>' element is the same look as <image-name> image
  • Then I expect the '<css>' element has look as <image-name> image with inconsistency of (\d*) percentage
  • Then I expect the element '<xpath|css>' has '<value>' value
  • Then I expect the '<xpath|css>' element is( not)? visible
  • Then I expect the element '<xpath|css>' is( not)? checked
  • Then I expect the element '<xpath|css>' is( not)? enabled
  • Then I expect the element '<xpath|css>' is( not)? disabled
  • Then I expect the element '<xpath|css>' is( not)? focus
  • Then I expect the element '<xpath|css>' is( not)? exist
  • Then I expect the '<xpath|css>' element has( not)? selected '<option>' option
  • Then I expect the '<xpath|css>' element has( not)? inner html '<inner-html>'
  • Then I expect the '<xpath|css>' element has( not)? element html '<element-html>'
  • Then I expect the '<xpath|css>' element has( not)? '<attribute-name>' attribute
  • Then I expect the '<xpath|css>' element has( not)? '<attribute-name>' attribute '<attribute-value>' value
  • Then I expect the '<xpath|css>' element( does not)? contains '<text>' text
  • Then I expect the '<xpath|css>' element has( not)? '<text>' text
  • Then I expect the '<xpath|css>' element has '<json-format-list-option>' options
  • Then I expect the '<xpath|css>' element count (\d*) present

Waiters Steps

When

  • When I wait a (\d*) seconds
  • When I wait for '<xpath|css>' element
  • When I wait for '<url>' url
  • When I wait for '<text>' text
  • When I wait for page to load
  • When I wait until '<xpath|css>' element enable
  • When I wait until '<xpath|css>' element not visible
  • When I wait for navigation

Console Steps

When

  • When I clear console

Then

  • When I expect that at least one console event with '<text>' text and '(log|debug|info|error|warning|trace)' type
  • When I expect that empty event with '<text>' text and '(log|debug|info|error|warning|trace)' type

Resource Requests(Response) Steps

When

  • When I clear the list of requests
  • When I wait until a request with '<url>' url is done
  • When I wait until a response with '<url>' url is done

Then

  • Then I expect that at least one resource requests made to '<url>' url
  • Then I expect that at least one resource requests made with '(GET|POST|PUT|DELETE)' method
  • Then I expect that a response was received with the (\d*) status
  • Then I expect that a response was received with the '{"content-type": /html/}' headers
  • Then I expect that a request contains the '{"status": "OK"}' post body
  • Then I expect that a response contains the '{"status": "OK"}' body
  • Then I expect that at least one request is still pending
  • Then I expect that requests with the (\d*) status does not exist

Dialogs Steps

When

  • When I dismiss the dialog
  • When I wait until the next dialog
  • When I accept the dialog
  • When I accept the '<text>' text dialog