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

wdio-wdiov5testrail-reporter

v1.0.37

Published

TestRail reporter for WebdriverIO v5+

Downloads

2,223

Readme

If you are using v8+, please use the official package at https://www.npmjs.com/package/@wdio/testrail-reporter

wdio-wdiov5testrail-reporter

TestRail reporter for versions 5 and 6 of WebdriverIO

Installation

npm install wdio-wdiov5testrail-reporter --save-dev

Usage

Add the following to wdio.conf

const testrailUtil = require('wdio-wdiov5testrail-reporter/lib');
  beforeSession: function (config, capabilities, specs) {
    testrailUtil.startup();
  },
  onComplete: (exitCode, conf, capabilities, results) => {
    testrailUtil.cleanup(conf); // This method returns the run id used
  },
  reporters: [
    ['wdiov5testrail', {
      domain: 'your domain',
      username: 'your testrail username',
      password: 'your testrail password (or api key)',
      projectId: your testrail project id,
      // See below for additional options
    }],
  ],

REQUIRED options

| Name | Description | | --- | --- | | domain | TestRail domain. Do not include protocol. | | username | TestRail username / email. | | password | TestRail API key. | | projectId | TestRail project id. |

OPTIONAL... options

| Name | Description | | --- | --- | | suiteId | TestRail suite id. Suite id for a multi-suite project Mandatory in multi-suite projects. Do not use in single-suite projects. | | title | Title of test run (or plan) to create. | | runId | TestRail run id. Update a specific run instead of creating a new run.| | useLatestRunId | true if updating latest run id instead of creating a new run. Defaults to false.| | version | Version tested, if required by TestRail instance. | | createTestPlan | If true, creates a test plan to which runs are added. Runs within are appended with the browser name. | | includeAll | true to include all tests in run, regardless of whether actually run by Webdriver.io. Defaults to true. | | strictCaseMatching | false to NOT throw an error if a test case found is not apart of the suite. Defaults to true. | | skippedStatusId | A custom status id assigned to skipped tests. If not assigned, skipped tests will be marked as status 4. | | closeTestRailRun | true to close test run in Test Rail after tests are complete. Defaults to false. | | casesFieldFilter | A {key: value} object to filter cases added to the test run, e.g. {'priority_id': 1, 'type_id': 2}. Values should be taken from TestRails. Running with empty value or with missing closeTestRailRun option will return a full list of cases. NOTE 1: if you use multiple key:value pairs in the filter object it will work as AND conditions. NOTE 2: casesFieldFilter takes into account only if includeAll=false|

Prefix all test assertions you wish to map with the test number.

Include the letter C.

 it(`C123 Can load the page`, function() {}

(optional) Add additional logging with addTestRailComment

const { addTestRailComment } = require('wdio-wdiov5testrail-reporter').default;
addTestRailComment('Will be added to test comment in TestRail');

Acknowledgement

@fijijavis - his reporter provided a solution for compiling test results