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 🙏

© 2026 – Pkg Stats / Ryan Hefner

testcafe-bugreplay

v1.0.4

Published

BugReplay's integration with the TestCafe automated e2e browser testing framework

Readme

BugReplay TestCafe Integration

The BugReplay TestCafe integration records screencasts of your automated TestCafe tests including timesynced JavaScript Console and Network logs

Installation

Install the package

npm install testcafe-bugreplay --save-dev

or if you prefer to use yarn

yarn add testcafe-bugreplay --dev

Configuration

Getting an API key

You will need to sign up for an account at https://bugreplay.com. After that you will need to login and get an API key by clicking the Hamburger Menu, click My Settings, and then Show API Key. You'll use this in the configuration file.

getting an API key

Adding the BugReplay Integration

In .testcaferc.json you'll need to tell Chrome to use the BugReplay Automation extension:

// .testcaferc.json
{
  "browsers": {
    "path": "/path/to/google-chrome",
    "cmd": "--no-first-run --no-default-browser-check --user-data-dir=/tmp/testcafe-chrome-profile --load-extension=./node_modules/bugreplay-automation/extension/ --auto-select-desktop-capture-source='Chrome'"
  }
}

After setting up this configuration you can have BugReplay record a fixture of tests by importing bugReplay and wrapping your fixture around this function and supplying an API key. For instance:

// test.js
import bugReplay from 'testcafe-bugreplay'

bugReplay(
  fixture `Getting Started`
    .page `http://devexpress.github.io/testcafe/example`,
  { apiKey: "YOUR API KEY GOES HERE"}
)
// ... your tests go here

All tests in this file would be recorded to BugReplay.

Running the Test

Running from Command Line

You can run the test directly by running the following in your terminal:

npx testcafe path/to/tests

Setting up a script

Inside of package.json add the following to the scripts object:

"scripts": {
  "test:testcafe": "testcafe path/to/tests"
}

You can name the script anything you'd like, it does not have to be test:testcafe.

Then in your command line run:

npm run test:testcafe

or

yarn test:testcafe

Note

You may be presented with a window, to select a screen to capture, during your test run, something like this: screen-capture

If you see the above screen during your test run, please check the file: .testcaferc.json and check the flag: --auto-select-desktop-capture-source='Entire screen'

Here are few options you can try:

  • In case you have an extended display connected, you can choose "Screen 1" or "Screen 2" depending on where your cypress test runner is running: --auto-select-desktop-capture-source='Screen 1' //or Screen 2

  • You can also provide the title of the browser window which testcafe launches while executing your tests. --auto-select-desktop-capture-source='<CHROME_WINDOW_TITLE>' //Check the share screen popup and look for the title of the window where your testcafe tests is running.

Limitations

This currently only works for Chrome. We're looking to expand to other browsers in the future.