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-acd-html-reporter

v2.0.3

Published

HTML TestCafe reporter plugin

Downloads

344

Readme

testcafe-reporter-acd-html-reporter

Build Status

This is the acd-html-reporter reporter plugin for TestCafe.

About

New in 2.0.1:

Added context menu for errors

New in 2.0.0:

Changed style of the reporter

Added test runs chart feature for single test

Added stable tests filter feature

Some bugs fixed

New in 1.5.8:

--days - to show test runs for X last days (14 by default)

New in 1.5.*:

Some fixes & impovements.

Tests in the report are only tests from the last run.

If to need to show tests from different jsons

New in 1.5:

Added statistics about previous tests runs.

New in 1.4:

Added correct error messages for hooks (before, after, etc).

Impoved errors text for all cases (added base TestCafe messages).

New in 1.3:

Added support of concurrency (also for Logger)

TS Logger moved from 'testcafe-reporter-acd-html-reporter/utils/Logger' to 'testcafe-reporter-acd-html-reporter/lib/Logger'

Added argument --appendLogs.

Argument --reportFile is applying by default

Added support npx acd-html-combine command

Added argument --logWarnings. If used, warnings will be logged to console after test run.

Reporter in .html format, for seeing it, you don't need to start any server. Except reporting to file, test run info duplicates in console.

concurrency

appendLogs

With definition --reportFile can be used to write results in one file with new name.

acd-html-combine

Result html file will be generated in base report folder with report-combined.json file with all files data.

If need to save combined report to a different path, use --dest (-dest) argument, e.g.: npx acd-html-combine test-results --dest 123.html npx acd-html-combine test-results -dest=path/to/123.html In that case report-combined.json will be in the same folder.

baseReportDir

If you need to run some times a day, save report, because old version with same date will be rewrited. You can save report to single file with a new name.

For extended test run information you can use Logger, implemented in the reporter. Method Logger.warn automatically sets status of a test: 'broken'.

Logger.warn('Something is strange in this test, may be bug, that 2+2=5 isn't truth');
await t.expect(2 + 2).eql(5);

Methods Logger.cleanUp and Logger.preconditions can be used in test hooks (beforeTest, afterTest, etc). It's equivalent of Logger.step, but without step number. Logger.step can be used with some steps as number, e.g. [1, 2, 3, 4], it will be showed in the report as Step 1-4.

Logger.step(1, 'Click the link and do something');
Logger.step([2, 3, 4], 'Doing something else');

Logger.info used for adding some information of test actions.

Logger.step(1, 'Click the link and do something');
await t.click('link');
Logger.info('Check that page opened');
await t.expect...

Install

npm install testcafe-reporter-acd-html-reporter

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 acd-html-reporter

If you want to have screenshots in report, use -s option:

testcafe chrome 'path/to/test/file.js' --reporter acd-html-reporter -s takeOnFails=true

you can add folder name to report (report will be saved as path/to/html/report.html and path/to/html/report.json):

testcafe chrome 'path/to/test/file.js' --reporter acd-html-reporter --reportFile path/to/html

or if the path ended with .html, report will be saved to it folder (path/to/my.html and path/to/report.json):

testcafe chrome 'path/to/test/file.js' --reporter acd-html-reporter --reportFile path/to/my.html

Author

Alex Chernik

Links

https://github.com/chalk/chalk https://devexpress.github.io/testcafe/documentation/extending-testcafe/reporter-plugin/helpers.html