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

grunt-painless-protractor

v0.0.2

Published

Grunt plugin for installing/setting up selnium protractor, and running tests against a local instance of your server

Downloads

7

Readme

grunt-painless-protractor

Grunt plugin for installing/setting up selnium protractor, and running tests against a local instance of your server

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-painless-protractor --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-painless-protractor');

The "painless_protractor" task

Overview

In your project's Gruntfile, add a section named painless_protractor to the data object passed into grunt.initConfig().

grunt.initConfig({
  painless_protractor: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
        config_file: 'protractor_config.js',
        webdriver_bin: 'webdriver-manager',
        protractor_bin: 'protractor',
        test_server: {
            cmd: 'node',
            args: ['server.js']
        }
    },
  },
});

What it does

Getting protractor up and running can be a real headache. This aims to take care of as much of the setup process as possible, but leaving protractor configuration to its own config file.

  • Ensures webdriver-manager is updated
  • Starts selenium webdriver
  • Optionally start an instance of your local server (useful for CI)
  • Run protractor tests using protractor install from node modules.

There is an optional override for webdriver_bin and protractor_bin path to use your systems own protractor or webdriver-manager binaries.

Options

options.config_file

Type: String

Path to your protractor config file

options.webdriver_bin

Type: String Default value: node_modules/protractor/bin/webdriver-manager

Path to webdriver-manager binary

options.protractor.bin

Type: String Default value: node_modules/protractor/bin/webdriver-manager

Path to protractor binary

Usage Examples

Default Options

TODO

Custom Options

TODO

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)