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

@rd-testrail-reporter/wdio

v7.1.2

Published

Web Driver IO reporter for Testrail.

Downloads

3

Readme

Table of Contents

Installation

npm install @rd-testrail-reporter/core @rd-testrail-reporter/wdio

Usage

Set the required environment variables TESTRAIL_API_USERNAME and TESTRAIL_API_PASSWORD. This can be done quite easily using a library like doenv. A .env file might look like this for example:

TESTRAIL_API_USERNAME="<your-username>"
TESTRAIL_API_PASSWORD="<your-password>"

In your wdio.conf file specify the reporter and options like:

import WDIOTestrailReporter from '@rd-testrail-reporter/wdio';

// ...
reporters: [
    [WDIOTestrailReporter, {domain: '<your-domain>', projectID: 0}]
]
// ...

In order to configure the reporter before Workers are spawned we need to call the start static method in the onPrepare callback in the wdio.conf file.

// ...
onPrepare: function (config) {
    WDIOTestrailReporter.start(config);
}
// ...

Cleanup

Cleaning up is just as simple as the start up, we simply need to call the end static method in the onComplete callback in the wdio.conf file.

onComplete: function() {
    WDIOTestrailreporter.end();
}

The start and end methods correlate to the start and end of a test run in Testrail and as such are essential.

More Info

How does this work?