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

@trint/testcafe-reporter-slack

v0.0.9

Published

TestCafe slack reporter plugin.

Downloads

13

Readme

TestCafe Reporter Slack

This package is a small modification of the original slack reporter.

We don't think there's much value on sending the error message to slack, as it polutes the channel and we won't be debugging the code there.

We also changed the emojis - from :heavy_check_mark: and :heavy_multiplication_x: to :white_check_mark: and :red_circle:. Reason being that it's imediately noticable which tests failed and which tests passed.

More variables: we show which environment the tests are running against, and we also show a link to the gitlab pipeline that trigger the tests to run.

Finally - if the any of the tests failed, then a small GoT shame gif is displayed at the end of the message.

testcafe-reporter-slack

This is a reporter for TestCafe. It sends the output of the test to slack.

Purpose

Once configured the repoter sends test results to Slack depending on a .env file from the folder the tests are run from

Setup instructions

Follow the instructions bellow to configure this plugin.

First install this package globaly to the machine you would like to run your tests on and then:

Testing

Running TestCafe with testcafe-reporter-slack.

In order to use this TestCafe reporter plugin it is necessary to define .env variables in your test project, hence the folder from where your call TestCafe.

  • cd into your test project.
  • Edit or create the .env file by adding the following ki-reporter required variables:
TESTCAFE_SLACK_WEBHOOK=https://hooks.slack.com/services/*****
TESTCAFE_SLACK_CHANNEL='#testcafe'
TESTCAFE_SLACK_USERNAME=testcafebot

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

const slack = require('@trint/testcafe-reporter-slack')

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

Further Documentation

TestCafe Reporter Plugins