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-reportportal-plugin

v0.6.6

Published

Report Portal TestCafe reporter

Downloads

19

Readme

This is the reportportal-plugin reporter plugin for TestCafe.

Integrate this Reporter in your project

Install the reporter via NPM

npm i testcafe-reporter-reportportal-plugin@latest --save-dev

Use the reporter in your TestCafe test run

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 reportportal-plugin

OR:

testcafe chrome 'path/to/test/file.js' --reporter=reportportal-plugin

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

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

Map of existing CLI Arguments:

| Required | Argument | Description | Example | | -------- | ---------- | --------------------------------------------------------------------------------------------------------------- | ------------------------------- | | Yes | rdomain | The domain of the report portal. https://{domain}/ | --rdomain=reports.pl.portal.com | | Yes | rtoken | The token to auth report portal with. Taken from the 'Profile' of your user. | --rtoken=gfkbv5994350mg | | Yes | rlaunch | The name of your launch. Required (Unless replaced by rlaunch-id argument). | --rlaunch=my-launch | | Yes | rproject | The name of your project. | --rproject=my-project | | No | rlaunch-id | The ID of an existing launch, can replace the rlaunch parameter. | --rlaunch-id=fjvkdnvjgnf | | No | rsuite | An optional suite name, adding a suite will put all tests under the suite instead of directly under the launch. | --rsuite=my-suite-name | | No | rprotocol | An optional ability to override the protocol of the API protocol. {protocol}://{domain}/. | --rprotocol=http | | No | disable-live-reporting | An optional ability to disable the live reporting | --disable-live-reporting |

Testing

Please go to the Testing section in the Contributing README file

Interested in contributing?

Please read our contributing guidelines here