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

@workco/wdio-watr-reporter

v0.0.11

Published

WebdriverIO plugin for creating test results in JSON format, specifically for WATR framework

Downloads

8

Readme

WDIO WATR REPORTER

A custom report for WebdriverIO projects looking to upload their results to the Work & Co Automation Test Reporter (WATR)

This project was derived from the 'wdio-junit-reporter' found here

Installation

The custom reporter can be installed via npm module by using the npm install command. We have hosted the reporter in our internal workco organization so you will need to include the @workco scope

npm i @workco/wdio-watr-reporter

Instructions on how to install WebdriverIO can be found here.

Configuration

After installing the custom reporter you will need include it in your test config file in order to add it to the Reporters option. Do not forget to include the @workco scope when importing.

NOTE: You must append .default when importing. This is due to some problems with ES6 imports in WDIO currently.

// wdio.conf.js
var customWatrReporter = require('@workco/wdio-watr-reporter').default;

After you have imported the custom report you can now add it to the reporters option in your WDIO config file. If you would like to run a stdout test report you can include it in the array with the imported custom report

// wdio.conf.js
module.exports = {
  // ...
  reporters: ['dot', customWatrReporter],

For the sake of maintaining consistent WATR index mappings we recommend setting reporterOptions with the combined property to true and also setting the outputDir to ./reports

// wdio.conf.js
module.exports = {
  // ...
  reporters: ['dot', customWatrReporter],
  reporterOptions: {
    outputDir: './reports'
  },
  // ...
};

By default the custom reporter pulls the name and version from your package.json file to build your filename. If you wish to specify a custom filename you can set the filename property.

// wdio.conf.js
module.exports = {
  // ...
  reporters: ['dot', customWatrReporter],
  reporterOptions: {
    outputDir: './reports',
    filename: 'wdio-results.json'
  },
  // ...
};

You can also choose to send the reporter output to the console (Stdout) instead of writing to a file:

// wdio.conf.js
module.exports = {
  // ...
  reporters: [customWatrReporter],
  reporterOptions: {
    useStdout: true
  },
  // ...
};

If you do not want to print out the mocha epilogue (i.e. 1 passing (5.2s)), you can suppress it:

// wdio.conf.js
module.exports = {
  // ...
  reporters: [customWatrReporter],
  reporterOptions: {
    suppressEpilogue: true
  },
  // ...
};

Upload to WATR

If you are using this custom report you are most likely interested in uploading your report to WATR, a system for aggregating and analysing test reports from all of Work & Co's internal projects using automated testing. Please visit the Workco-Selenium-Common home page for information regarding uploading your test results.