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

testcafe-reporter-chrome-recorder

v0.1.2

Published

chrome-recorder TestCafe reporter plugin.

Downloads

1

Readme

testcafe-reporter-chrome-recorder

Build Status

This is the chrome-recorder reporter plugin for TestCafe. Its purpose is to record video of the test run in Chrome browser (including headless mode).

Note that it has severe performance impact so it's not recommended to run in concurrent mode.

Install

Install ffmpeg and make sure it's available in PATH

npm install testcafe-reporter-chrome-recorder

Usage

When you run tests from the command line, specify the reporter name by using the --reporter option:

testcafe chrome 'path/to/test/file.js' --reporter spec,chrome-recorder:/dev/null

When you use API, pass the reporter name to the reporter() method:

testCafe
    .createRunner()
    .src('path/to/test/file.js')
    .browsers('chrome')
    .reporter('chrome-recorder') // <-
    .run();

Options

Environmental variables that allow you to change reporter behaviour:

  • CHROME_RECORDER_TMP_DIR
    Temporary directory where images with single frames will be stored. They will be removed after the conversion to mp4.
    Default: /tmp/chrome-recorder
  • CHROME_RECORDER_OUTPUT_DIR
    Output directory for video file
    Default: process.cwd()
  • CHROME_RECORDER_FRAME_FORMAT
    Output format for captured frames. Either jpeg or png. Default: jpeg

Known issues

This is just a draft so expect many issues :)

  1. Performance impact on test execution
  2. Frames are a bit out of sync

Author

Andrzej Pasterczyk