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

wd-cucumber

v0.1.9

Published

Framework wrapper on webdriver.io + cucumber

Downloads

2

Readme

webdriver-io-cucumber

Simple "ready for action" BDD solution based on webdriver-io and cucumber

Options for gulp task 'test':

  --version        Show version number                                 [boolean]
  --env, -e        Run tests on specified env with cread definded in
                   config/creds file                                  [required]
  --url, -u        Run tests on specified url, for default - base url for
                   specified environment
  --browser, -b    Run tests on specified browser, for default - Chrome
  --user, -l       Run tests on env with user login different from default for
                   this env
  --password, -p   Run tests on env with password different from default for
                   user specified in config/creds
  --tags, -t       Run scenarios with specified tags. If needs more than 1 tag,
                   it should be separated by commas
  --instances, -i  Run scenarios in parallel with specified number of browser
                   instances. For default: 1
  --help           Show help                                           [boolean]

Examples:

Run tests

    gulp test -e prd -i 4 -t "@smoke"

Create html report

    gulp report -e prd

If you need to test Angular app, add 'rootElement' into wdio.conf.js:

    rootElement: '<your_angular_root_element>'

Example of page object for Angular app

const AngularPage = require('wd-cucumber').AngularPage;

class Home extends AngularPage {
    constructor(selector = '.screen-fill-body', url = '/'){
        super(selector,url);
        this.defineComponent('Menu', new Menu());
        this.defineComponent('Packages', new Packages());
    }
}

Run tests in parallel with different credentials:

  1. Start credential server (server example here)
  2. Add credental manager functions in tests
    • Get sessionId from createSessionId(<your_host:port>)

    • Create user pool createUserPool(<your_host:port>, <your_env>, [{user: <user>, password: <password>}], sessionId)- before tests start (for example in wdio.config -> onPrepare()). Be aware, these functions are async!

    • Use lockUser()/unlockUser() for get and free user credential. For example:

            `browser.call(async () => credentials = await mg.lockUser('http://localhost:3002', <your_env_name>));`
    • Delete user pool from server, after tests were done: deleteUserPool(<your_host:port>, <your_env>, sessionId)