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

testrail-wdio-reporter-2022

v1.1.0

Published

Create a run on testrail and the update the test cases results, with the option to close the test run

Downloads

5

Readme

testrail-wdio-reporter-2022

Create a run on testrail and the update the test cases results Use test rail API https://www.gurock.com/testrail/docs/api/reference

The first thing you need is to enable the TestRail API so that report can communicate with TestRail and push the test results. To do so, log into your TestRail account and go to Administration > Site Settings > API and make sure you click the checkbox near Enable API.

After this, you'll need to create an API key from a user on your Testrail instance, by going to My Settings > API Keys.

Features

  • Webdriver/IO Custom Reporter
  • Creates new test run to publish results and can optionally close that test run
  • Test run name can be customized and will have date and time appended
  • Further features and functionality can be added by editing ..\node_modules\testrail-wdio-reporter-2022\src\testrail-reporter.js in your project or by forking this project

Usage/Examples

Add the required options to your WDIO config file

const TestrailReporter = require('testrail-wdio-reporter-2022');

    reporters: 
        [[TestrailReporter, {
        projectId: 1,
        suiteId: 1,
        domain: 'xxxxx.testrail.io or com',
        username: 'userEmail',
        apiToken: 'testrail apitoken',
        runName: 'name for the test run' ,
        closeRun: true
    }]],

Configuration

    projectId: ID of the testrail project
    suiteId: ID of the suit, if there is not suits 1 is default 
    domain: your-domain.testrail.com', // no default, required field
    username: 'userEmail', // no default, required field
    apiToken: 'testrail apitoken', // no default, required field
    runName: 'name for the test run'
    closeRun: true/false //required field. True if you want the run to be closed after execution. Otherwise false