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

abe-protractor

v0.1.3

Published

A Protractor JS pre-processor to load ABE Specs as Angular Mocks

Downloads

12

Readme

Build Status Dependency Status devDependency Status Monthly downloads License

API By Example helper for Protractor

This repository includes tools to be able to use the ABE format from within JS code. In particular we aim to support Protractor JS tests.

Usage

In order to use abe-protractor you will need to add the setup service stubs, using Protractor's onPrepare within your protractor-conf file.

### mocksLocation

This is the location of your ABE mock files, in which to cycle through.

stubsLocation

Type: String Required

This is the location in which your manually created Stubs are kept, the file locations should mirror those found within mocksLocation.

log

Type: Boolean Default: false

This flags whether or not you wish abe-protractor to log out when stubs have been created during the setup of running Protractor tests.

Example folder structure (desc could be users):

mocks/                      -> Base of your Mock storage
    mock-desc               -> Your container for your Mock
        post.json           -> The POST example of your API Mock
        get.json            -> The GET of singular resources within response example of your API Mock
        put.json            -> The PUT example of your API Mock
        query.json          -> The GET of multiple resources within response example of your API Mock
stubs/
    stub-desc
        mock-desc.stub.js   -> Stub for your Mock

Example Usage:

var abeProtractor = require('abe-protractor');

onPrepare: function () {
    abeProtractor.setupServiceStubs({
        mocksLocation: 'mocks/**/*',
        stubsLocation: 'stubs/',
        log: true
    });
}

It is expected that all of your ABE-Spec mocked JSON files are located in the same folder (or at least the same parent folder).

Do I have to make my stubs?

If you do not require any custom stubs you can use abe-protractor's default builder for stubs. Using your mock JSON files it will create your stubs for you, based on the information within your JSON spec.

To take a look at the stub that is generated take a look here.