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

cypress-circleci-reporter

v0.3.0

Published

Cypress test reporter for CircleCI

Downloads

452,340

Readme

cypress-circleci-reporter

CircleCI npm GitHub

Cypress test reporter for CircleCI based on mocha-junit-reporter. Helps with test parallelization.

Requirements

  • Cypress 3.8.3 or newer

Installation

$ npm install cypress-circleci-reporter mocha --save-dev
$ yarn add cypress-circleci-reporter mocha --dev

Usage

After installing the reporter, you'll need to modify your config to use it:

CircleCI config example

run_cypress_tests:
  parallelism: 3        # or any other number that suits your needs
  steps:
    # some previous steps

    - run:
        name: Run cypress tests
        command: yarn cypress run --spec "$(circleci tests glob "./cypress/integration/**/*.spec.js" | circleci tests split --split-by=timings | paste -sd "," -)" --reporter cypress-circleci-reporter

    - store_test_results:
        path: test_results
    - store_artifacts:
        path: test_results

First test run with this config should create and store reports for each test file. These will be used during next runs to determine timings of each test. CircleCI will then split the test files between available containers to speed up the process.

Configuration options

Options can be passed to the reported by adding --reporter-options parameter to the CLI command.

Example: --reporter cypress-circleci-reporter --reporter-options "resultsDir=./results/cypress,resultFileName=result-[hash]"

| Parameter | Default | Effect | | -------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | project | undefined | If you use Cypress' project parameter, this should be set to the same value. | | resultsDir | ./test_results/cypress | Name of the directory that reports will be saved into. | | resultFileName | cypress-[hash] | Name of the file that will be created for each test run. Must include [hash] string as each spec file is processed completely separately during each cypress run execution. |