Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2024 – Pkg Stats / Ryan Hefner

pecode_cypress

v1.0.0

Published

a year ago

A set of pre-installed deps and structure

Downloads

6

0High
0Medium
0Low

Usage

Before running the test for the first time, install node.js(only once).

Install dependencies:

npm install

Run the tests:

npm run test:chrome

Passing :headless will force the browser to be hidden.

Open the cypress test editor:

npm run test:debug

Technologies

Project is created with:

Cypress version: ^7.4.0
Mocha : ^8.2.1
Page Object pattern

About Cypress

JavaScript End to End Testing Framework.
Cypress has been made specifically for developers and QA engineers, to help them get more done.
Cypress benefits from our amazing open source community - and our tools are evolving better and faster than if we worked on them alone.
Cypress takes snapshots as your tests run. Simply hover over commands in the Command Log to see exactly what happened at each step.
Debug directly from familiar tools like Chrome DevTools. Our readable errors and stack traces make debugging lightning fast.
Cypress automatically reloads whenever you make changes to your tests.
Cypress automatically waits for commands and assertions before moving on. No more async hell.

Directory structure

fixtures - contains test data.
integration - contains integration test files.
methods - takes the selectors from the page object and uses them to create methods such as login, create something new, edit something, delete something etc.
page-object folder- contains the page selectors.
plugins/index.js - import external plugins for Cypress or add code that runs in Node instead of browser.
If screenshots were taken via the cy.screenshot() command or automatically when a test fails, the screenshots are stored in the screenshotsFolder which is set to cypress/screenshots by default.
support
- commands.js - allows to create custom commands and overwriting existing commands.
- index.js - allows to put reusable behavior such as custom commands or global overrides that you want applied and available to all of your spec files.
cypress.json - the first time you open Cypress Test Runner, it creates the cypress.json configuration file. This JSON file is used to store any configuration values you supply.