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 🙏

© 2025 – Pkg Stats / Ryan Hefner

testcafe-reporter-db

v0.0.8

Published

db TestCafe reporter plugin.

Downloads

1,572

Readme

testcafe-reporter-db

Build Status npm version

This is the db reporter plugin for TestCafe.

Table of Contents

DB Engines supported

  • MySQL

Getting Started

Installation

npm install testcafe-reporter-db

Initial Configuration

In order to use the reporter correctly, you have to edit or create the .env file, by adding the following required environment variables:

Database connection details /play 56k

TESTCAFEREPORTER_DB_USERNAME=
TESTCAFEREPORTER_DB_PASS=
TESTCAFEREPORTER_DB_HOST=

Database and table details

TESTCAFEREPORTER_DB_DB=
TESTCAFEREPORTER_DB_RUN_RESULTS_TABLE=
TESTCAFEREPORTER_DB_TEST_TABLE=

Tescafe Reporter configuracion. If you are interested in store each test result, you should use 1. If you are interested in store only failed results, the value should be 0.

TESTCAFEREPORTER_DB_TESTSTORED=
TESTCAFEREPORTER_DB_DEVICE=
TESTCAFEREPORTER_DB_BROWSER=
TESTCAFEREPORTER_DB_ENV=
TESTCAFEREPORTER_DB_OTHER_RUN=
TESTCAFEREPORTER_DB_OTHER_TEST=

Database Configuration

  • Run_results_table

Fields:

| Field | Type | Lenght | Allow Null | Extra | | ------------- | ------------- | ------------- | ------------- | ------------- | | id | Int | 11 | No | auto_increment | | date | Datetime | | No | auto_increment | | run_number | Int | 11 | No | None | | run_result | Varchar | 1 | No | None | | test_total | Int | 4 | No | None | | test_passed | Int | 4 | No | None | | test_failed | Int | 4 | No | None | | test_skipped | Int | 4 | No | None | | test_duration | Varchar | 10 | No | None | | test_device | Varchar | 50 | Yes | None | | test_browser | Varchar | 150 | Yes | None | | test_environment | Varchar | 50 | Yes | None | | test_other_1 | Varchar | 50 | Yes | None |

  • run_result : 0 if the run passed. 1 if the run failed.
  • Test_results_table

| Field | Type | Lenght | Allow Null | Extra | | ------------- | ------------- | ------------- | ------------- | ------------- | | id | Int | 11 | No | auto_increment | | run_number | Int | 11 | No | None | | fixture_name | Varchar | 1000 | No | None | | test_name | Varchar | 1000 | No | None | | test_result | Int | 1 | No | None | | test_other | Varchar | 100 | No | None |

  • test_result : 0 if the test passed. 1 if the test failed. 2 if the test was skipped

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 db

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

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

Roadmap

Contributing

  • If you want to suggest a change, feature or any question, feel free to open an issue or a pull request.

License

This project is licensed under the MIT License - see the LICENSE.md file for details

Author

+Based on testcafe-reporter-list+

Acknowledgments