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

plus.cucumber.code

v1.0.7

Published

Cucumber's code support

Downloads

5

Readme

Feature: Cucumbers code support

I want to write documentation that always works.

Our tests - our documentation.

Scenario: Should allow to define code inline and assert results (digits) 

Given code `var money = 100`                                             
Then `money` should equal `100`                                          

Scenario: Should allow to define code in the box and assert results (strings) 

Given code:                                                                   
  """
  ```
    var money = 101;
    var name = 'plus';

  ```
  """
Then `money` should equal `101`                                               
Then `name` should equal 'plus'                                               
Then `name` should equal `'plus'`                                             
Then `name` should equal "plus"                                               
Then `name` should equal `"plus"`                                             

Scenario: Should allow to define code in the box and assert results (objects/functions) 

Given code:                                                                             
  """
  ```
    var myFunction = function (){
      return 200;
    }

    var MyClass = function (){
      this.name = 'my name'
    }

  ```
  """
Then `myFunction()` should equal `200`                                                  
Then `new MyClass().name` should equal `'my name'`                                      

Scenario: Should allow to assert types and variables 

Given code `var MyClass = function(){}`              
Given code `var instance = new MyClass()`            
Then `instance` should be instanceOf `MyClass`       
Then `instance` should be ok                         

Scenario: Should allow to assert with should chain 

Given code `var name = 'plus'`                     
Then `name` should be ok                           
Then `name` should not be false                    

Scenario: Should allow to write doc blocks 

Given @doc this is inline documentation    
Given @doc:                                
  """
   this is box of documentation
  """

Scenario: Should allow to require relative module 

Given require `src/Code.js` as `Code`             
Then `Code` should be ok                          

Scenario: How to use? 

Given @doc `npm install plus.cucumber.code --save-dev`       
Given @doc Simply add code.js file to features folder        
Given @doc:                                                  
  """
  ```
  // file: features/code.js

  module.exports = require('plus.cucumber.code');

  ```
  """
Given @doc or `node_modules/.bin/plus.cucumber.code.js init` 
Given @doc it will create code.js from previous doc box.     

8 scenarios (8 passed) 27 steps (27 passed)