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

sealights-cucumber-plugin

v2.0.97

Published

Cucumber integration for sealights

Downloads

2,487

Readme

sealights-cucumber-plugin

This is the sealights plugin for Cucumber.js.

Install

npm install sealights-cucumber-plugin

Usage

Pass path-to-plugin as require option of cucumber command

npx cucumber-js ./features ... --require <path-to-plugin>

Or set it in config file

// cucumber.js
module.exports = {
  default: {
    ...
    require: [
      './features/support/*',
      '<path-to-plugin>',
    ]
  }
};

Note: Usage of --require option override default definition of path to step definitions. Pass it explicitly if you don't do it yet. Example:

npx cucumber-js ./features --require ./src/steps/*.steps.ts --require <path-to-plugin>

Resolve path to plugin

Resolve path to plugin dynamically

CommonJs

const pathToPlugin = require.resolve('sealights-cucumber-plugin');

ESM

import url from 'node:url';

const pluginUrl = import.meta.resolve('sealights-cucumber-plugin');
const pathToPlugin = url.fileURLToPath(new URL(pluginUrl));

Resolve in CLI

Execution of next command allow to resolve path in CLI if node available on machine

Unix:

SL_PACKAGE=$(node -p "require.resolve('sealights-cucumber-plugin')")

PowerShell:

$Env:SL_PACKAGE = node -p "require.resolve('sealights-cucumber-plugin')"

If any of this option don't work for you can use static path to plugin ./node_modules/sealight-cucumber/plugin/tsOutputs/lib/cucumber-integration.js But it is not recommended and it can be changed.

Usage in protractor.conf or wdio.conf

Pass path-to-plugin as require option of cucumber command

cucumberOpts: {
    require: [
      './src/steps/*.steps.ts',
      '<path-to-plugin>'
    ]
  },

Passing parameters

Passing parameters to plugin via config file

Create a file sl.conf and fill it with config in JSON format

{
  tokenfile: <path/to/token-file>,
  buildsessionidfile: <path/to/buildSessionId-file>,
  testStage: e2e,
}

Passing parameters to reporter via CLI

!!! Not recommended. This case won`t work in the latest version of cucumber, use file config instead

From the command line add sealights parameters with --sl- prefix

npx cucumber-js ./features --sl-tokenfile <path/to/token-file>  --sl-buildsessionidfile <path/to/buildSessionId-file> --sl-testStage e2e

Supported parameters

  • token - Sealights token
  • tokenFile - Path to file contains the Sealights token
  • buildSessionId - Sealights build session id
  • buildSessionIdFile - Path to file contains the Sealights build session id
  • testStage - Test stage current tests are relates to
  • labId - Pre-defined Sealights lab-id (optional)
  • proxy - Proxy server (optional)

Author

Sealights