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

@sentinel-one/testcafe-reporter-html

v1.4.5

Published

The HTML reporter for TestCafe

Downloads

5

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

zdenek.bednarzdenek.bednardmytro.skliarenkodmytro.skliarenkodanielle_galdanielle_galanujyadavsentineloneanujyadavsentineloneshilpa-s1shilpa-s1velsonjrvelsonjrudays1udays1radek_pleskac_s1radek_pleskac_s1attilahazayattilahazaydenys-klepikovdenys-klepikovzlatkos1zlatkos1tanmayidtanmayidshua.mshua.myuliana.baryskinayuliana.baryskinadans1dans1igorchornyiigorchornyipavel.skopikpavel.skopikjanhorajanhoranpm_service_s1npm_service_s1sentinelonesentineloneassafaassafaofir.fridmanofir.fridmanirenavirenavyoni12abyoni12abkoralbenamikoralbenamiliorl3009liorl3009gal.falahgal.falahmatansmatansjp-s1jp-s1vovadevvovadevyamarbelyamarbelyoavscyoavscfrontend-npm-groupfrontend-npm-groupmaayanbmaayanb

Keywords

testcafereportertestsautomatedjavascriptpluginhtml

Readme

testcafe-reporter-html

PICUS' HTML reporter generator for TestCafe automated tests. It provides an HTML report of a TestCafe task(s) execution, as well as feedback on the errors, if these occurred. Also it provides an easy way to view the screenshots from failing tests.

Build Status

Testcafé Reporter HTML

Table of Contents

Installation and setup

1. Install package

$ npm install testcafe-reporter-html

2. Add the reporter flag to your test task runner

$ testcafe chrome test_folder/ --reporter html

3. Configure the output file

By default the html is written to stdout. To write the html to a file use the TestCafe build-in method:

$ testcafe chrome test_folder/ --reporter html:path/to/my/file.html

Contributing

If you'd like to contribute a feature or bugfix: Thanks! To make sure your fix/feature has a high chance of being included, please read the following guidelines:

  1. Post a pull request.
  2. Make sure there are tests! We will not accept any patch that is not tested. It's a rare time when explicit tests aren't needed. If you have questions about writing tests for testcafe-reporter-html, please open a GitHub issue.

Please see CONTRIBUTING.md for more details on contributing and running test.

Thank you to all the contributors!

By participating in this project, you agree to abide by the PICUS code of conduct.

LICENSE

MIT License - PICUS