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

kommando

v1.0.0

Published

Configurable cross browser functional / acceptance test launcher (using Webdriver)

Downloads

35

Readme

kommando

Build Status

kommando is a configurable cross browser functional / acceptance test launcher (using Webdriver).

It helps you to get started writing functional cross browser tests using JavaScript without knowing details how to properly setup the various Webdriver servers locally, while still allowing to run your created tests on an existing Selenium Grid (including SauceLabs).

For each test launch you can configure a test-runner that should be used to execute tests (currently jasmine-node, mocha) or cucumber and you can tell which Webdriver JS lib should be used to create a Webdriver client session (e.g. selenium-webdriver, leadfoot, wd or cabbie) per browser. The configured Webdriver client session then gets injected into the test runner execution context and can then be used there.

This project is aimed for finding the best suited approach to write your functional cross browser tests using JavaScript by allowing you to choose a test style (jasmine, mocha) you already are familiar with and using a Webdriver JS library that you like the most. To simplify working with the promise-based API of selenium-webdriver kommando contains runner modules that tie the test runner to the control-flow of this promise-based API.

Prerequisites

  • Java (>= 1.7 if you want to use iOS-Driver)
  • [optional] Appium (can be installed through npm install appium -g)

Installation

npm install kommando -g

Executing REPL

Kommando provides a REPL runner which you can use to play with an individual Webdriver library.

# REPL with selenium-webdriver library and phantomjs
kommando --runner repl
# REPL with selenium-webdriver library and chrome
kommando --runner repl --browser chrome
# REPL with leadfoot
kommando --runner repl --browser chrome --client leadfoot
# REPL with cabbie
kommando --runner repl --browser chrome --client cabbie
# REPL with wd
kommando --runner repl --browser chrome --client wd
# REPL with wd-promise
kommando --runner repl --browser chrome --client wd-promise

Writing your first functionl test for kommando

// mytest.js (using jasmine syntax)
describe('github', function() {
  it('reads the "title"', function(done) {
    // the global "kommando.browser" provides the initialized Webdriver session
    // using "selenium-webdriver" as default Webdriver library
    kommando.browser.get('https://www.github.com').then(function() {
      return kommando.browser.findElement(kommando.webdriver.By.className('heading'));
    }).then(function(heading) {
      return heading.getText();
    }).then(function(text) {
      expect(text).toBe('Build software better, together.');
    }).then(done, done); // handle promise error / success within "it"
  });
});

Executing that test

You can invoke kommando either via command-line:

# this will execute your test using PhantomJS (default)
kommando mytest.js

or via Node.js:

// also executing tests using PhantomJS
var kommando = require('kommando');
kommando({
  tests: ['./mytest.js']
});

Executing test in Chrome, Firefox and PhantomJS using CLI:

kommando -b chrome -b firefox -b phantomjs mytest.js

or via Node.js:

var kommando = require('kommando');
kommando({
  browsers: ['chrome', 'firefox', 'phantomjs'],
  tests: ['./mytest.js']
});

Credits

Thanks to Protractor for the initial idea of this project and its jasminewd helper.