Awesome

Spectacular

Spectacular is a <abbr title='Behavior-Driven Development'>BDD</abbr> framework for CoffeeScript and JavaScript whose attempt to bring the power of RSpec to JavaScript. Spectacular try to favor the best practices used for writing better RSpec tests in its design.

This is the kind of tests you can write with Spectacular:

describe Array, ->
  given 'item', -> foo: 'bar'

  it -> should exist

  itsInstance 'length', -> should equal 0

  describe '::indexOf', ->
    context 'with an item not present in the array', ->
      itsReturn with: (-> [@item]), -> should equal -1

    context 'with an item present in the array', ->
      subject 'array', -> [@item]

      specify 'the returned value', ->
        expect(@array.indexOf @item).to equal 0

Features, the short tour

Conditioned Specs
Matcher based description
Implicit subjects
Describe auto-subject
Factories
JSON and HTML fixtures (and more)
Promised-based tests run
Synchronous and asynchronous matchers
Synchronous and asynchronous tests
Browser support
Shared examples
Custom matchers
CSS-queries expressions to test the DOM content
Strings and objects diff in comparison results
The API is provided with both camelCase and snake_case version
No external dependencies in browsers

For more information view the documentation

Install

Spectacular is available as a npm module, you can then install it with:

npm install -g spectacular

This will install Spectacular globally and allow you to use the Spectacular command line tool.

Command-line

The most simple way to use the spectacular command line tool is as follow:

spectacular test specs/**/*.spec.js

Commands

<table cellspacing="0"> <tr> <td>`test`</td> <td>Runs the tests on NodeJS.</td> </tr> <tr> <td>`server`</td> <td>Starts a server. The specs can then be accessed from a browser at the the following address: `http://localhost:5000`. The default port can be changed by setting the `PORT` environment variable.</td> </tr> <tr> <td>`phantomjs`</td> <td>Assuming you have PhantomJS installed, it will starts a server and run the test on PhantomJS.</td> </tr> <tr> <td>`slimerjs`</td> <td>Assuming you have SlimerJS installed, it will starts a server and run the test on SlimerJS.</td> </tr> </table>

Options

<table cellspacing="0"> <tr> <td>`-c, --coffee`</td> <td>Add support for CoffeeScript files. You can now run your specs with: `spectacular --coffee specs/**/*.coffee`.</td> </tr> <tr> <td>`-f, --format`</td> <td>Select the console output format (progress|documentation).</td> </tr> <tr> <td>`-r, --require PATH`</td> <td>Adds `PATH` to the array of paths to includes.</td> </tr> <tr> <td>`-v, --verbose`</td> <td>Enable verbose output.</td> </tr> <tr> <td>`-t, --trace`</td> <td>Enable stack trace report for failures (default is `true`).</td> </tr> <tr> <td>`--long-trace`</td> <td>By default the stack traces are cropped after 6 lines to limit the amount of output. You can display the full stack trace with this option.</td> </tr> <tr> <td>`-p, --profile`</td> <td>Add a report with the 10 slowest examples at the end of the output.</td> </tr> <tr> <td>`-d, --documentation`</td> <td><strong>deprecated</strong> Use the format option instead</td> </tr> <tr> <td>`-s, --server`</td> <td><strong>deprecated</strong> Use the `server` command instead.</td> </tr> <tr> <td>`--phantomjs`</td> <td><strong>deprecated</strong> Use the `phantomjs` command instead.</td> </tr> <tr> <td>`--phantomjs-bin PATH`</td> <td>Pass the path to the PhantomJS binary.</td> </tr> <tr> <td>`--slimerjs-bin PATH`</td> <td>Pass the path to the SlimerJS binary.</td> </tr> <tr> <td>`--source GLOB`</td> <td></td> </tr> <tr> <td>`--map, --source-map`</td> <td>Enable the support for CoffeeScript source map on both node and browsers. When using this mode with the browser without relying on the Spectacular server additional setup is required, please see the [Source Map Support](http://abe33.github.com/spectacular/#Source-Map-Support) section of the documentation for details.</td> </tr> <tr> <td>`-m, --matchers PATH`</td> <td><strong>deprecated</strong> Use `--require PATH` instead.</td> </tr> <tr> <td>`--helpers PATH`</td> <td><strong>deprecated</strong> Use `--require PATH` instead.</td> </tr> <tr> <td>`--fixtures PATH`</td> <td>Specify the path where project fixtures can be found, by default fixtures are loaded from `./specs/support/fixtures`.</td> </tr> <tr> <td>`--no-trace`</td> <td>Remove stack trace from failures reports.</td> </tr> <tr> <td>`--random`</td> <td>Enable tests randomization.</td> </tr> <tr> <td>`--no-random`</td> <td>Disable tests randomization.</td> </tr> <tr> <td>`--seed INT`</td> <td>Sets the seed for the tests randomization.</td> </tr> <tr> <td>`--colors`</td> <td>Enable coloring of the output.</td> </tr> <tr> <td>`--no-colors`</td> <td>Disable coloring of the output.</td> </tr> <tr> <td>`--no-matchers`</td> <td><strong>deprecated</strong> Don't require you matchers instead.</td> </tr> <tr> <td>`--no-helpers`</td> <td><strong>deprecated</strong> Don't require your helpers instead.</td> </tr> </table>

Options can also be defined in a .spectacular file at the root of your project.

Contributing

I decided to start using the AngularJS commit messages convention for this project. Please use the same convention as well for commits in PR.

I also try to follow Nvie's Successful Git Branching Model. Meaning that I do the daily work in the develop branch and try to keep the master branch with only the released versions. All the pull request should be done to the develop branch.