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 🙏

© 2026 – Pkg Stats / Ryan Hefner

testcafe-cucumber

v0.1.0

Published

An integration of TestCafe and CucumberJS

Readme

Introduction

mipart-frontend-test is used for automating E2E test on Mipart site

Prerequisite

Dependency Installation

Run npm install to install dependencies

Test Execution

  • Run npm run test-safari-mac in case of executing test on Safari browser using MAC OS
  • Run npm run test-safari-win in case of executing test on Safari browser using Windows OS
  • Run npm run test-chrome-mac in case of executing test on Chrome browser using MAC OS
  • Run npm run test-chrome-win in case of executing test on Chrome browser using Windows OS
  • Run npm run test-safari-1-mac in case of executing test on Safari browser using @at001 tag-name and MAC OS
  • Run npm run test-safari-1-win in case of executing test on Safari browser using @at001 tag-name and Windows OS
  • Run npm run test-safari-report-mac in case of executing test on Safari browser then generating test report using MAC OS
  • Run npm run test-safari-report-win in case of executing test on Safari browser then generating test report using Windows OS For more details, please refer to package.json file

Test Report

Please find the generated report in reports folder

Project Structure

  • Page elements are located in features\sut\pages folder
  • Step definitions of each page are located in features\step_definitions folders
  • Feature files are located in features folder
  • Configuration file is package.json file