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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@qanalyzer/forge-wdio

v1.2.1

Published

QAnalyzer WebdriverIO reporter + service — ingest or file modes via @qanalyzer/forge-commons

Readme

@qanalyzer/forge-wdio

WebdriverIO reporter + service for QAnalyzer (Jira Forge quality hub).

Supports WebdriverIO 8+ with Mocha (@wdio/mocha-framework) or Cucumber (@wdio/cucumber-framework).

Install

# Mocha (default)
npm install -D @qanalyzer/forge-wdio @qanalyzer/forge-commons @wdio/mocha-framework

# Cucumber
npm install -D @qanalyzer/forge-wdio @qanalyzer/forge-commons @wdio/cucumber-framework

Configure — Mocha

// wdio.conf.js
const QaWdioReporter = require('@qanalyzer/forge-wdio').default;
const { beforeRunHook, afterRunHook, QaWdioService } = require('@qanalyzer/forge-wdio');

exports.config = {
  specs: ['./test/specs/**/*.spec.js'],
  baseUrl: 'https://www.saucedemo.com',
  framework: 'mocha',
  reporters: [
    [
      QaWdioReporter,
      {
        // Defaults to mode=off (no credentials required)
        // mode: 'ingest' | 'file' | 'off',
        // projectKey: 'DEMO',
        disableWebdriverStepsReporting: true, // default
      },
    ],
  ],
  services: [[QaWdioService, {}]],
  capabilities: [
    {
      browserName: 'chrome',
      'goog:chromeOptions': { args: ['--headless', '--disable-gpu'] },
    },
  ],
  onPrepare: async function () {
    await beforeRunHook();
  },
  onComplete: async function () {
    await afterRunHook();
  },
};

Configure — Cucumber

// wdio.cucumber.conf.js
const QaWdioReporter = require('@qanalyzer/forge-wdio').default;
const { beforeRunHook, afterRunHook, QaWdioService } = require('@qanalyzer/forge-wdio');

exports.config = {
  specs: ['./test/features/**/*.feature'],
  framework: 'cucumber',
  cucumberOpts: {
    require: ['./test/step-definitions/**/*.js'],
  },
  reporters: [
    [
      QaWdioReporter,
      {
        useCucumber: true, // scenario → one result; Gherkin steps → meta.qa.steps
        disableWebdriverStepsReporting: true,
      },
    ],
  ],
  services: [[QaWdioService, {}]],
  onPrepare: async () => { await beforeRunHook(); },
  onComplete: async () => { await afterRunHook(); },
};

Tag conventions:

  • Prefer Jira keys in the scenario title or bare tags: @AUTH-101
  • Optional metadata: @suite=Checkout, @title=…, @tags=smoke,e2e

See examples/single/wdio/wdio.cucumber.conf.js.

Required for ingest/file: onPreparebeforeRunHook and onCompleteafterRunHook.

Modes

| Mode | Behavior | | ---- | -------- | | off (default) | No network / file write | | file | Writes the ingest payload (default ./qanalyzer-results.json) | | ingest | POSTs the payload with format: jest-json |

Env: QANALYZER_MODE, QANALYZER_PROJECT_KEY, QANALYZER_INGEST_URL, QANALYZER_INGEST_TOKEN, QANALYZER_LAUNCH_NAME.

Helpers (Mocha)

const { qa } = require('@qanalyzer/forge-wdio');
const LoginPage = require('../pageobjects/LoginPage');

describe('Login', () => {
  it('AUTH-101 User can login with valid credentials', async () => {
    qa.fields({ severity: 'critical', layer: 'e2e' });
    qa.suite('E-commerce\\tAuthentication\\tLogin');

    await qa.step('Open login page', async () => {
      await LoginPage.open();
      await expect(LoginPage.usernameInput).toBeDisplayed();
    });

    await qa.step('Login', async (step) => {
      await step.step('Fill credentials', async () => {
        await LoginPage.login('standard_user', 'secret_sauce');
      });
    });
  });
});

Prefer Jira issue keys in test titles. Use await qa.step() for step timelines (including nested step.step()).

qa.attach({ type: 'text/plain', ... }) uploads via Forge when content/path is set (still-image / small files). Use type, not contentType.

Run

QANALYZER_MODE=off npx wdio run wdio.conf.js
QANALYZER_MODE=off npx wdio run wdio.cucumber.conf.js