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-test-reporter-service

v9.0.12

Published

WebdriverIO server to send reporter data to testreporter.io

Downloads

213

Readme

WebdriverIO Test Reporter Service

WDIO service that takes results from wdio-test-reporter and uploads them to testreporter.io

testreporter.io stores and tracks all test runs with extensive details about each test. This gives you a historical overivew of how your tests are running.

Setup is very simple. All you need to do is add the service and reporter to the services and reporters arrays in your wdio.conf.js file.

Install the service

npm install wdio-test-reporter-service

Add the service to the services array in wdio.conf.js

services: [['test-reporter', {
	reporterOutputDir : `./testreporter`,      // This must match the outputDir from the wdio-test-reporter
	username          : `[email protected]`,  // console.testreporter.io username
	apiToken          : `12345`,               // Found in the console.testreporter.io under your proifle section
	projectId         : 123,                   // Only needed if using more than one project
	codeVersion       : `2.8.10`,              // The code version can also be set here
}]],

Add the wdio-test-reporter to the reporters array in wdio.conf.js

npm install wdio-test-reporter
reporters : [[`test`, {
	outputDir : `./testreporter`
}]]

Environment variables

Environment variables can be set when running tests that the server will use to add to the results

  • RUN_TITLE - Title of the test run. This might be somthing like a Jira issue key. Defaults to a timestamp if not specified
  • RUN_UUID - UUID which can be used to directly link to the test run results. e.g. https://console.testreporter.io/runs/
  • CODE_VERSION - Set the version of code this test run ran against