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

@factorial/stack-e2e

v0.2.2

Published

This is the end-to-end testing package for `@factorial/stack-core`. It uses [cypress](https://www.npmjs.com/package/cypress).

Downloads

701

Readme

@factorial/stack-e2e

This is the end-to-end testing package for @factorial/stack-core. It uses cypress.

Installation

You can install it via:

yarn factorial init

or manually via:

yarn add @factorial/stack-e2e

Make sure it is added to your .factorialrc.js like this:

// .factorialrc.js

module.exports = {
  use: [require("@factorial/stack-e2e")],
};

Usage

This package exposes a test task to core, which means that every time you run yarn factorial test it would be executed together with tests provided by other packages.

If you want to run only the end-to-end tests, you can run:

yarn factorial test --only e2e

Configuration

Cypress has different types of configuration:

  • Module API configuration: https://docs.cypress.io/guides/guides/module-api#Options
  • Configuration: https://docs.cypress.io/guides/references/configuration

The default Module API configuration provided by this package is kept very minimal:

{
  "configFile": false,
  "exit": true,
  "headless": true,
  "quiet": true
}

If you want to overwrite this, you can do that in the .factorialrc.js:

// .factorialrc.js

module.exports = {
  use: [
    [
      require("@factorial/stack-e2e"),
      { … } // config object
    ]
  ],
};

If you want to overwrite the normal configuration, you have two options:

  1. Set a config key in the object shown in the solution above
  2. Create a cypress.json (including your options) and add configFile: "./cypress.json" to the object shown in the solution above

Running cypress headed

By default cypress is run headless. If you want the browser to open when running the tests, you need to set the following in the Module API configuration:

{
  "headless": false,
  "headed": true
}

Files created by cypress

Please note that by default cypress e.g. creates screenshots and videos. These should most likely not be committed to your git repository, so you might want to add the paths, where they are stored (see https://docs.cypress.io/guides/references/configuration#Folders-Files), to your .gitignore.