Just some boilerplate for common JS testing setups.
Switch branches/tags
Nothing to show
Pull request Compare This branch is even with studiomohawk:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
jasmine
mocha-chai
mocha-node-should
qunit
README.md

README.md

JavaScript testing boilerplate

JavaScript testing frameworks require a lot of boilerplate. I grew tired of of having to set up all the files for every project, thus I decided to maintain this repo to quickly cp them into my project.

The different testing frameworks need different files, so I made a folder for each combination I used so far.

Usage

$ git clone https://github.com/js-coder/js-testing-boilerplates.git
$ cd yourProject # A git repo
$ cp -r ../js-testing-boilerplates/mocha-chai/* .
$ make init-testing

Submodules / NPM

All vendor files are added with git submodules or NPM, so you can easily update them.

Makefile

Each boilerplate folder contains a Makefile with these tasks:

  • make init-testing: Initialise the git submodules. Run this after cping the boilerplate.
  • make update-testing: Updates the node packages and / or the git submodules.
  • make test: Run the test suite, with the framework's command line tool or grunt + PhantomJS.

The folders also contain grunt files, so you can easily re-run the tests when files change.

$ grunt watch

mocha-node-should doesn't contain grunt, but a make test-w task.

Travis

Configuration for the travis continuous integration service is on board too!