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

yattex

v2.3.0

Published

Commands to run: yattex (in your test script)

Downloads

95

Readme

Yattex CLI based test tool

Commands to run:

  • npm install
  • In your test script add yattex
  • npm test

How it works.

We are using mocha js and jest for testing. For reporting we use mochawesome reporters and for jest we use Jest-stare.

when we start testing using this " npm test " user need to input custom test decorators on console and after this all the test case run and store results in .yattex/run-{timestamp} folder. All the work done on real time.

After test case completed our tool command, its generate .yattex folder and .yattex/run-${timestamp} folder. Inside .yattex/run-${timestamp} this folder add custom decorators list in decorators.json file. This tool also check if this project have a git then it create a git.json file and store git branch name and project name inside it.

In Cypress, to add screenshots to the Html report, add this on top of the cypress/support/e2e.js file

import addContext from "mochawesome/addContext";

After that add this block:

Cypress.on("test:after:run", (test, runnable) => {
  if (test.state === "failed") {
    const screenshot = `../../cypress/screenshots/${Cypress.spec.name}/${runnable.parent.title} -- ${test.title} (failed).png`;
    addContext({ test }, screenshot);
  }
});