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

testingbot

v0.1.1

Published

a wrapper for camme/webdriverjs to ease testingbot.com testing

Downloads

5

Readme

Soda

Selenium Node Adapter. A light-weight Selenium RC client for NodeJS, forked from Soda with support for TestingBot

Installation

via npm:

$ npm install soda

Authors

Running Examples

The examples provided in ./examples are intended to be run against Selenium RC, which can be downloaded here. Once installed simply execute the following command to start the selenium server:

$ java -jar selenium-server.jar

Then choose an example to run using soda:

$ node examples/google.js

Actions

"Selenese" actions include commands such as open and type. Every action has a corresponding Client method which accept a variable number of arguments followed by a callback Function which receives any potential err, the response body, and response object itself.

browser.session(function(err){
  browser.open('/', function(err, body, res){
    browser.type('q', 'Hello World', function(err, body, res){
      browser.testComplete(function(){
        
      });
    });
  });
});

Because nested callbacks can quickly become overwhelming, Soda has optional chaining support by simply utilizing the .chain getter as shown below. If an exception is thrown in a callback, or a command fails then it will be passed to end(err). The .chain getter should only be used once, activating the chaining api.

browser
  .chain
  .session()
  .open('/')
  .type('q', 'Hello World')
  .end(function(err){
    browser.testComplete(function() {
      console.log('done');
      if(err) throw err;
    });
  });

When chaining successful commands may receive a callback, which is useful for custom assertions:

browser
  .chain
  .session()
  .open('/')
  .getTitle(function(title){
    assert.equal('Hello World', title);
  })
  .end(function(err){
    browser.testComplete(function() {
      console.log('done');
      if(err) throw err;
    });
  })

With the .and() method you can add additional commands to the queue. The callback accepts the client instance, which is also the value of "this".

For example you may want to authenticate a user, note we do not use .chain or .end() again, this simply extends the current queue.

function login(user, pass) {
  return function(browser) {
    browser
      .open('/login')
      .type('username', name)
      .type('password', pass)
      .clickAndWait('login');
  }
}

With this helper function we can now re-use this logic in several places, an express the tests in a more logical manor.

browser
  .chain
  .session()
  .open('/')
  .assertTitle('Something')
  .and(login('foo', 'bar'))
  .assertTitle('Foobar')
  .and(login('someone', 'else'))
  .assertTitle('Someone else')
  .end(function(err){
    browser.testComplete(function() {
      console.log('done');
      if(err) throw err;
    });
  });

Selenium RC Example

var soda = require('soda')
  , assert = require('assert');

var browser = soda.createClient({
    host: 'localhost'
  , port: 4444
  , url: 'http://www.google.com'
  , browser: 'firefox'
});

browser
  .chain
  .session()
  .open('/')
  .type('q', 'Hello World')
  .clickAndWait('btnG')
  .getTitle(function(title){
    assert.ok(~title.indexOf('Hello World'))
  })
  .end(function(err){
    browser.testComplete(function() {
      console.log('done');
      if(err) throw err;
    });
  });

TestingBot Example

var soda = require('soda')
  , assert = require('assert');

var browser = soda.createTestingBotClient({
    'url': 'http://sirrobertborden.ca.app.learnboost.com/'
  , 'os': 'Linux'
  , 'browser': 'firefox'
  , 'browser-version': '3.'
  , 'max-duration': 300 // 5 minutes
});

// Log commands as they are fired
browser.on('command', function(cmd, args){
  console.log(' \x1b[33m%s\x1b[0m: %s', cmd, args.join(', '));
});

browser
  .chain
  .session()
  .setTimeout(8000)
  .open('/')
  .waitForPageToLoad(5000)
  .clickAndWait('//input[@value="Submit"]')
  .clickAndWait('link=Settings')
  .type('user[name][first]', 'TJ')
  .clickAndWait('//input[@value="Save"]')
  .assertTextPresent('Account info updated')
  .clickAndWait('link=Log out')
  .end(function(err){
     browser.testComplete(function(){
       console.log(browser.jobUrl);
       if (err) throw err;
     });
  });  

Creating Helpers

Keep in mind you can extend the prototype as needed for your test. An example of this which we frequently use is waitForDialog(). Since the exports of require('soda') is the Client itself we can extend it as shown below, in our case waiting for an element with the class of ".dialog" to be present.

soda.prototype.waitForDialog = function() {
  return this.waitForElementPresent('css=.dialog');
};

Running The Test Suite

First we need to start Selenium RC:

 $ java -jar selenium-server.jar

Then run:

 $ make test

More Information

License

(The MIT License)

Copyright (c) 2010 LearnBoost <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.