A test-driven JS assessment
I want to work on the tests; what do I do?
Note that on Windows, there are some reports that you will need to restart after installing Node - see #12.
You can clone or download this repo. Once you have done so, from the root directory of the repo, run:
npm install node bin/serve
You can then view the tests in your browser at http://localhost:4444.
When you visit that page, all of the tests should be failing; your job is to
get the tests to pass. To do this, you'll need to refer to the tests in the
files in the
tests/app directory, and edit the files in the
Once you update a test, you can reload the test page in the browser to see
whether it worked.
You can also run (most of) the tests on the command line:
The command line runner is a work in progress; contributions welcome :)
You can also develop with live-reload and grunt-watch if that's your thing:
npm install -g grunt-cli npm install grunt develop
I need help!
There may be friendly folks willing to help you in #js-assessment or #jshotline on freenode IRC.
I want to contribute tests; what do I do?
Submit a pull request! The tests are currently loosely organized by topic, so
you should do your best to add tests to the appropriate file in
create a new file there if you don't see an appropriate one. If you do create
a new file, make sure to add it to
tests/runner.js, and to add a stub for the
solution to the corresponding file in
app/. Finally, it would be great if you
could update the answers
Any substantial contributions will be duly credited in the readme, as well as of course in the git commit log.
If your tests need data that can be fetched via XHR, stick a
.json file in
data directory; you can access it at
The repo includes jQuery, Backbone, Underscore, and RequireJS. If there's other
stuff you'd find useful, you can put it in the
I want to see the answers!
First, bear in mind that looking up the answers is going to teach you a whole lot less than you'll learn by working on the tests, even if you occasionally get stuck. I'd recommend only looking at the answers once you have the tests passing, to see if there's another way you could have approached the problem. When you're ready to look at the answers, you can find them here; I'll do my best to keep them up to date.
I hate <some technology you've chosen>
This repo uses RequireJS for dependency management and Mocha and expect.js for the tests themselves. It uses the BDD style for authoring tests. If this doesn't suit you, please fork away, or, better, submit a pull request that lets this be more flexible than it currently is.
There are a number of things that would make this project better; check out the issues for details, pull requests welcome!
Copyright © 2012 Rebecca Murphey.
This work is licensed under the Creative Commons Attribution-Share Alike 3.0 license. You are free to share and remix the work, and to use it for commercial purposes under the following conditions:
- Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
- Share Alike — If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
Any of these conditions can be waived if you get permission from the copyright holder.