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-cucumber2-framework

v0.0.4

Published

A WebdriverIO plugin. Adapter for Cucumber2 testing framework.

Downloads

7

Readme

WDIO Cucumber Framework Adapter

Build Status Code Climate Test Coverage dependencies Status


A WebdriverIO plugin. Adapter for CucumberJS testing framework.

Installation

The easiest way is to keep wdio-cucumber-framework as a devDependency in your package.json.

{
  "devDependencies": {
    "wdio-cucumber-framework": "~1.0.0"
  }
}

You can simple do it by:

npm install wdio-cucumber-framework --save-dev

Instructions on how to install WebdriverIO can be found here.

Configuration

Following code shows the default wdio test runner configuration...

// wdio.conf.js
module.exports = {
  // ...
  framework: 'cucumber'
  cucumberOpts: {
    timeout: 10000
  }
  // ...
};

cucumberOpts Options

backtrace

Show full backtrace for errors.

Type: Boolean Default: false

compiler

Require files with the given EXTENSION after requiring MODULE.

Type: String[] Default: *[]* Example: ['js:babel-core/register']

failFast

Abort the run on first failure.

Type: Boolean Default: false

name

Only execute the scenarios with name matching the expression (repeatable).

Type: REGEXP[] Default: []

snippets

Hide step definition snippets for pending steps.

Type: Boolean Default: true

source

Hide source uris.

Type: Boolean Default: true

profile

Specify the profile to use.

Type: String[] Default: []

require

Require files/dir before executing features. If you apply a path don't use globbing as it is not supported by Cucumber. Instead just reference the directory where you step definitions are located (e.g. /path/to/definitions instead of /path/to/definitions/*).

Type: String[] Default: []

snippetSyntax

Specify a custom snippet syntax.

Type: String Default: undefined

strict

Fail if there are any undefined or pending steps

Type: Boolean Default: false

tags

Only execute the features or scenarios with tags matching the expression. Note that untagged features will still spawn a Selenium session (see issue webdriverio/webdriverio#1247). The recommended way to specify a subset of feature files is to use suites. Using ['@t1,@t2'] will run scenarios tagged with @t1 OR @t2 whilst ['@t1', '@t2'] will run those with @t1 AND @t2.

Type: String[] Default: []

timeout

Timeout in milliseconds for step definitions.

Type: Number Default: 30000

ignoreUndefinedDefinitions

Please note that this is a wdio-cucumber-framework specifc option and not recognized by cucumber-js itself Treat undefined definitions as warnings.

Type: Boolean Default: false

failAmbiguousDefinitions

Please note that this is a wdio-cucumber-framework specifc option and not recognized by cucumber-js itself Treat ambiguous definitions as errors.

Type: Boolean Default: false

Development

All commands can be found in the package.json. The most important are:

Watch changes:

$ npm run watch

Run tests:

$ npm test

# run test with coverage report:
$ npm run test:cover

Build package:

$ npm build

For more information on WebdriverIO see the homepage.