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

gherkin-mocha

v0.0.5

Published

Basic cucumber impl. based on Mocha, Phantom and Webdriver

Downloads

10

Readme

Gherkin Mocha

Combining both Gherkin and Mocha, as a phantomjs or node runner.

Description

This module implements a basic parser on top of cucumber/gherkin JS implementation, to match Gherkin keywords and structure into Mocha Suite and Test.

It can be seen as some sort of special Mocha UI, using both .feature files to express the specs, and steps files to define how the tests are implemented.

Borrows a lot to Cucumber, without being a strict and valid Cucumber implementation.

TODO: Background, table and examples.

Examples

PhantomJS

Using phantomjs environment, steps written using PhantomJS API.

# For phantomjs
phantomjs bin/gherkin-mocha-phantom --stepdir test/phantom-steps test/features/browse.feature

Using PhantomJS in Webdriver mode

Using nodejs environment, steps written in node using Webdriver API.

phantomjs --webdriver=9134

# in another shell
./bin/gherkin-mocha --stepdir test/node-steps test/features/browse.feature

Features

A basic example.

Feature: Node Runner

  Willing to quickly assert nodejs / phantom runner

  Scenario: Searching gherkin
    Given I browse URL "http://google.com"
    Then I fill "gherkin" in "q"
    And I submit the form "[action='/search']"
    And I want to render the page at "debug.png"

Please note that only Feature, Scenarios, Given, When, Then and the And keywords are supported, and only basic support.

Further work is needed to bridge stuff like Background, Example tables, Step tables etc. to Mocha land.

Steps

Steps are written in node or phantom, using three global function helpers: Given, When, Then.

They're just semantic sugar, they're handled exactly the same by the framework.

The --stepdir option is used to tell the system where to load them (not recursively, but you can require from there)

// Node
Given(/I browse URL "([^"]+)"/, function(url, done) {
  var wd = require('wd');

  if (!this.driver) this.driver = wd.remote(webdriverHost, webdriver);

  var driver = this.driver;
  driver.init(function(err) {
    if (err) return done(err);
    // driver#get should errback on invalid URL
    driver.get(url, done);
  });
});

// Phantom
Given(/I browse URL "([^"]+)"/, function(url, done) {
  var page = this.page = require('webpage').create();
  page.open(url, function(status) {
    if (status !== 'success') return done(new Error('Error opening URL ' + url + '. Status: ' + status));
    done();
  });
});