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

protractor-http-mock-sample-plugin

v0.0.1

Published

Sample plugin for protractor-http-mock

Downloads

25

Readme

Protractor Mock Sample Plugin

This is a sample plugin and only intended to be used as an example of how to create a plugin for protractor-http-mock.

What are plugins for?

Plugins allow you to extend the matching capabilities of protractor-http-mock to allow for custom logic unique to your application. In other words, it allows you to extend the rules used to match a request from your application to a provided mock request on your test.

Creating your own plugin

Create an NPM module that provides an object with a match function:

module.exports = {
	match: function(mockRequest, requestConfig){

	}
};

mockRequest object is the mock currently being checked to see if it matches the actual request your app made.

requestConfig is the config object from the request the app made.

protractor-http-mock expects a truthy or falsy value to indicate a successfull match or not.

Note

Note that your plugin code will only execute if all other standard checks pass since it runs at the end of the chain.