Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Gerbil: Inquisitive, friendly animals that rarely bite, TDD for the rest of us

branch: master

Merge pull request #11 from gusaaaaa/master

assertThrow should rise an error if expected and thrown errors don't match
latest commit ba3a1879ba
Bruno Aguirre authored
Octocat-spinner-32 lib Fixes matching errors problem in assertThrow method April 16, 2013
Octocat-spinner-32 test Fixes matching errors problem in assertThrow method April 16, 2013
Octocat-spinner-32 .travis.yml Ready to CI March 08, 2012
Octocat-spinner-32 Makefile Add Makefile September 05, 2011
Octocat-spinner-32 README.md Fixes some grammar on README April 03, 2013
Octocat-spinner-32 package.json Version Bump May 10, 2012
README.md

Gerbil

Build Status

Gerbil!

n. Gerbils: Inquisitive, friendly animals that rarely bite, TDD for the rest of us

Gerbil attemps to be an uber simple and minimalistic testing framework for javascript.

Now with npm

$ npm install gerbil

Or just include the .js and run tests within a normal browser.

You can now execute the tests with node without depending on the browser

var scenario = require('gerbil').scenario;

scenario("Testing with node", {
  "should work in a terminal": function(g){
    g.assert(true);
  }
});

// Or if you want to access some global Gerbil stuff

var Gerbil = require('gerbil');
var scenario = Gerbil.scenario;

What's included?

assert

Good ol' assert, checks boolean.

assertEqual

Just like assert but checks types AND value.

assertThrow

Asserts an exception throw.

assertType

Asserts the type of the object to evaluate.

pending

Marks the test as pending.

setTimeout

Runs the test within a set time.

async

Runs async code. Eg. callbacks, timers.


Example output

Console Errors

Console Errors

Walkthrough

// Name the scenario you want to test and pass an object with your tests.
scenario("Some useful stuff that needs to work", {
  // Reserved names are 'setup', 'before', 'after' and 'cleanup'. They define
  // the steps to be executed.
  //
  // Every test gets one parameter, this is the test suite itself.
  // Modifying 'this' will affect the context in the tests, it's useful when
  // using 'setup' to initialize some state.
  'setup': function(g) {
    this.validName = 'Gerbil';
  },
  // Within the test 'this' gets the config defined in 'setup'
  'should get the correct name': function(g) {
    g.assertEqual(this.validName, 'Gerbil');
  },

  // Test in the feature, useful to test future events or timers.
  'in the future': function(g) {
    this.time = new Date().getTime();

    g.setTimeout(function() {
      g.assert(new Date().getTime() > this.time);
    }, 1000);
  },

  // Test async code.
  //
  // Using the async function you can control the status of the test. This is
  // really useful when you are testing callbacks.
  // But remember, it's your responsability to end() the test.
  'should be able to test asyncronous code': function(g) {
    var asyncStuff = function() {
      this.callback = null;
    };

    asyncStuff.prototype = {
      eventually: function(fn) {
        this.callback = fn;
      },

      exec: function() {
        setTimeout(function(c) {
          c.callback();
        }, 500, this);
      }
    };

    g.async(function() {
      var async = new asyncStuff;
      async.eventually(function() {
        g.assert(true);
        // end() will end the current scenario and trigger a summary
        g.end();
      });
      async.exec();
    });
  }

});

Example

scenario("This is my scenario", {
  "setup":  function() {
    // When scenario starts
    this.someThing = new Thing;
  },
  "before": function() {
    // Before every test
    this.someThing.magic_magic();
  },
  "after":  function() {
    // After every test
    this.someThing.clean();
  },
  "cleanup": function() {
    // When the scenario ends
    this.someThing = false;
  },

  "MagicThing should have a length": function(g) {
    this.someThing.add(1);
    g.assertEqual(this.someThing.length, 1);
  },

  "MagicThing should be valid": function(g) {
    g.assert(this.someThing.valid);
  }
});

Scenario config and global config.

var myCoolFormatter = {
  // Passing tests
  "ok": function(msg) {},

  // Failing tests
  "fail": function(msg) {},

  // Pending tests
  "pending": function(msg) {},

  // The start of a scenario
  "scenario": function(msg) {},

  // Report at the end of a scenario
  "summary": function(msg) {}
};

scenario("Fancy scenario", {
  "config": function(c) {
    c.formatter = myCoolFormatter;
  },
  "somewhere over the rainbow": function(g) {
    g.assert(false);
  }
});

// Or if you want to affect every gerbil scenario

Gerbil.globalConfig = {
  formatter: myCoolFormatter
}

Callbacks

Withing the config object you can add two types of callbacks, 'start' and 'finish'. This can help you trigger events after the scenario is finished or a nice sand clock when it starts.

scenario('configuration', {
  'config': function(c) {
    c.start = function(object) {};
    c.finish = function(results) {};
  }
});

// Of course you can define then globally:

Gerbil.globalConfig = {
  start: function(object) {},
  finish: function(results) {}
};

What's the catch?

The results are only shown in the console, the one from console.log if you use it in a browser. Run it with an open inspector or define a custom formatter if you want prettier results. And in the bottom you will find the summary

Browser tests

TODO

  1. Get a gerbil as a pet

Contributors

Something went wrong with that request. Please try again.