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

@bdt-hub24/core-hubplaywright-framework

v1.4.1

Published

This framework uses Playwright, Cucumber, Node and Typescript as the underlying tech stack

Downloads

37

Readme

This framework uses Playwright, Cucumber, Node and Typescript as the underlying tech stack

The code is committed to GIT and the repo name is HubPlaywright. The main branch is the prod branch and will always be in a fit to run state. Prior approval is needed before committing anything to the main branch, as this might start failing the CI/CD pipelines.

GIT URL: https://hub24.visualstudio.com/Agility/_git/HubPlaywright

To setup the framework on your local machine, you need to create this folder structure in C: C:/GIT_Automation and then download the repo in HubPlaywright folder inside C:/GIT_Automation

Clone the above repo at C:/GIT_Automation/HubPlaywright

Now open Webstorm and select Open Folder. Install these plugins in Webstorm,

.env Files Support

Batch Scripts Support

Cucumber+

Properties

Open C:/GIT_Automation/HubPlaywright/e2e folder in Webstorm.

Once the project loads in Webstorm, open the terminal within the IDE and run the below commands in order,

npm init npx -p typescript tsc --init npm add playwright -D npm add @playwright/test -D npm add @cucumber/cucumber -D npm add typescript -D npm add ts-node -D npx playwright install npm install dotenv --save npm add cucumber-html-reporter

Once these NPM packages are successfully installed locally, the framework is all set to run.

To run the tests, execute: ./run_tests.bat

This command will execute all the feature files in src/features

All the page files must be placed inside src/step_definitions/assertions and must be named as abc.pages.ts

This ensures that page files are separeted from other files